Search Postgresql Archives

Re: Indexes mysteriously change to ON ONLY

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <tgl@xxxxxxxxxxxxx> wrote:
Rumpi Gravenstein <rgravens@xxxxxxxxx> 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 ONLY *chapter USING btree (dur_uk,
>> catalog_id)

What do you mean "somehow changed"?  There is nothing in the system
catalogs that stores that exact string, so I suppose what you mean
is that some tool is presenting the indexes to you that way.

If that tool is pg_dump, this is its normal behavior.  There will
be other commands in its output that build the rest of the
partitioned index set.

                        regards, tom lane


--
Rumpi Gravenstein

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux