Postgres Pro
Downloads
Home   >   mailing lists

Opclass parameters of indexes lost after REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Michael Paquier
Subject Opclass parameters of indexes lost after REINDEX CONCURRENTLY
Date
Msg-id YX0CG/QpLXcPr8HJ@paquier.xyz
Whole thread Raw
Responses Re: Opclass parameters of indexes lost after REINDEX CONCURRENTLY
List pgsql-hackers
Tree view 
Hi all,

While reviewing the code for opclass parameters with indexes, I have
noticed that opclass parameters are lost after a concurrent reindex.
As we use a IndexInfo to hold the information of the new index when
creating a copy of the old one, it is just a matter of making sure
that ii_OpclassOptions is filled appropriately, but that was missed by
911e702.

Attached is a patch to fix the issue.  After a concurrent reindex, we
would not finish with a corrupted index, just with one rebuilt with
default opclass parameter values.

Any objections or comments?
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.
Next
From: Bharath Rupireddy
Date:
Subject: Re: logical decoding/replication: new functions pg_ls_logicaldir and pg_ls_replslotdir