Re: unique, partitioned index fails to distinguish index key fromINCLUDEd columns
| От | Justin Pryzby |
|---|---|
| Тема | Re: unique, partitioned index fails to distinguish index key fromINCLUDEd columns |
| Дата | |
| Msg-id | 20190115023022.GJ15177@telsasoft.com обсуждение исходный текст |
| Ответ на | Re: unique, partitioned index fails to distinguish index key fromINCLUDEd columns (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: unique, partitioned index fails to distinguish index key fromINCLUDEd columns
|
| Список | pgsql-hackers |
On Mon, Jan 14, 2019 at 07:31:07PM -0300, Alvaro Herrera wrote: > On 2019-Jan-09, Justin Pryzby wrote: > > > -- Fails to error > > postgres=# CREATE UNIQUE INDEX ON t(j) INCLUDE(i); > > > > -- Fail to enforce uniqueness across partitions due to failure to enforce inclusion of partition key in index KEY > > postgres=# INSERT INTO t VALUES(1,1); > > postgres=# INSERT INTO t VALUES(2,1); > > Doh. Fix pushed. Commit 8224de4f42cc should have changed one > appearance of ii_NumIndexAttrs to ii_NumIndexKeyAttrs, but because of > the nature of concurrent development, nobody noticed. I figured as much - I thought to test this while trying to fall asleep, without knowing they were developed in parallel. Should backpatch to v11 ? 0ad41cf537ea5f076273fcffa4c83a184bd9910f Thanks, Justin
В списке pgsql-hackers по дате отправления: