Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour.
От | Alvaro Herrera |
---|---|
Тема | Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour. |
Дата | |
Msg-id | 20180329160406.ii2wgbkmlnfxtwbt@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour. (Rushabh Lathia <rushabh.lathia@gmail.com>) |
Ответы |
Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour.
|
Список | pgsql-hackers |
Rushabh Lathia wrote: > On Thu, Mar 29, 2018 at 7:46 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> > wrote: > > Hmm, offhand I don't quite see why this error fails to be thrown. > > ATTACH PARTITION should throw an error, because partition table "foo" > already have two partition with key values (1, 2,3 4). And table "foo_d" > which we are attaching here has : Oh, I understand how it's supposed to work. I was just saying I don't understand how this bug occurs. Is it because we fail to determine the correct partition constraint for the default partition in time for its verification scan? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: