| From: | Rumpi Gravenstein <rgravens(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Indexes mysteriously change to LOG |
| Date: | 2023-01-27 20:23:08 |
| Message-ID: | CAEpg1wBr_apWFXwUOYuU=rz4q=CJ6xmed282CmYM0HQMm3eWFg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rumpi Gravenstein | 2023-01-27 20:24:02 | Re: Indexes mysteriously change to ON ONLY |
| Previous Message | Peter J. Holzer | 2023-01-27 18:03:46 | Re: timestamptz, local time in the future, and Don't do it wiki |