Re: Indexes mysteriously change to ON ONLY

[Rumpi Gravenstein <rgravens@xxxxxxxxx>]

Whoops ... fixed the subject line.

On Fri, Jan 27, 2023 at 3:23 PM Rumpi Gravenstein <rgravens@xxxxxxxxx> 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)

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

--

Rumpi Gravenstein