Postgres Pro
Downloads
Home   >   mailing lists

Indexes mysteriously change to LOG - Mailing list pgsql-general

From Rumpi Gravenstein
Subject Indexes mysteriously change to LOG
Date
Msg-id CAEpg1wBr_apWFXwUOYuU=rz4q=CJ6xmed282CmYM0HQMm3eWFg@mail.gmail.com
Whole thread Raw
Responses Re: Indexes mysteriously change to LOG
List pgsql-general
Tree view
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)

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

pgsql-general by date:

Previous
From: "Peter J. Holzer"
Date:
Subject: Re: timestamptz, local time in the future, and Don't do it wiki
Next
From: Rumpi Gravenstein
Date:
Subject: Re: Indexes mysteriously change to ON ONLY