Re: Indexes mysteriously change to LOG
От | Adrian Klaver |
---|---|
Тема | Re: Indexes mysteriously change to LOG |
Дата | |
Msg-id | 27ccec91-9ff2-b566-efb1-e1c552563514@aklaver.com обсуждение исходный текст |
Ответ на | Indexes mysteriously change to LOG (Rumpi Gravenstein <rgravens@gmail.com>) |
Ответы |
Re: Indexes mysteriously change to LOG
|
Список | pgsql-general |
On 1/27/23 12:23, Rumpi Gravenstein wrote: > We are on PostgreSQL 14.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) > 8.5.0 20210514 (Red Hat 8.5.0-10), 64-bitPostgreSQL 14.5 on > x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat > 8.5.0-10), 64-bit > > We have recently discovered that on some of our partitioned tables > indexes that were created as: > > CREATE UNIQUE INDEX chapter_u01 USING btree (dur_uk, catalog_id) How did you do the above without the table name? > > somehow changed to include the ON ONLY option: > > CREATE UNIQUE INDEX chapter_u01 *ON ONLY *chapter USING btree (dur_uk, > catalog_id) > > There is no SQL issued that explicitly requests this "ON ONLY" option. > I am wondering if this is a side-effect of some other activity. > Googling and looking through documentation haven't helped. > > Does anyone have any thoughts on how this might happen? > > -- > Rumpi Gravenstein -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: