Re: Indexes mysteriously change to ON ONLY - Mailing list pgsql-general

From Tom Lane
Subject Re: Indexes mysteriously change to ON ONLY
Date
Msg-id 3567881.1674852814@sss.pgh.pa.us
Whole thread Raw
In response to Re: Indexes mysteriously change to ON ONLY  (Rumpi Gravenstein <rgravens@gmail.com>)
Responses Re: Indexes mysteriously change to ON ONLY
List pgsql-general
Rumpi Gravenstein <rgravens@gmail.com> 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



pgsql-general by date:

Previous
From: Rumpi Gravenstein
Date:
Subject: Re: Indexes mysteriously change to LOG
Next
From: Rob Sargent
Date:
Subject: nextval per counted