I cheat by using sed to remove "ONLY ON " from the CREATE statements.
On 1/27/23 15:30, Rumpi Gravenstein wrote:
Tom/Christophe I now understand. Thanks for the clear explanation.
On Fri, Jan 27, 2023 at 4:16 PM Tom Lane wrote:
Rumpi Gravenstein writes:
> We are using the
Tom/Christophe I now understand. Thanks for the clear explanation.
On Fri, Jan 27, 2023 at 4:16 PM Tom Lane wrote:
> Rumpi Gravenstein writes:
> > We are using the pg_indexes view (indexdef) to retrieve the index
> > definition.
>
> Ah.
>
> > Are you saying that as a normal part of building
Rumpi Gravenstein writes:
> We are using the pg_indexes view (indexdef) to retrieve the index
> definition.
Ah.
> Are you saying that as a normal part of building an index, there are short
> periods of time where the pg_indexes view will show the index with ON ONLY
> specified?
No, there's no
> On Jan 27, 2023, at 13:01, Rumpi Gravenstein wrote:
>
> We are using the pg_indexes view (indexdef) to retrieve the index definition.
This is as expected. Once the index is created on the partitioned set of
tables, the index on the *root* table will be ON ONLY that table; the child
We are using the pg_indexes view (indexdef) to retrieve the index
definition.
Are you saying that as a normal part of building an index, there are short
periods of time where the pg_indexes view will show the index with ON ONLY
specified?
On Fri, Jan 27, 2023 at 3:53 PM Tom Lane wrote:
> Rumpi
Rumpi Gravenstein writes:
>> 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
Whoops ... fixed the subject line.
On Fri, Jan 27, 2023 at 3:23 PM 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
