Re: Add support for ALTER INDEX .. ALTER [COLUMN] col_num {SET,RESET}

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Subject: Re: Add support for ALTER INDEX .. ALTER [COLUMN] col_num {SET,RESET}
Date: 2021-10-29 09:10:22
Message-ID: YXu6fryfVdP/
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Oct 29, 2021 at 02:09:34PM +0900, Michael Paquier wrote:
> The attached does the work, with tests and documentation added to all
> the places I could think about while reviewing the existing opclass
> code for indexes. There is no need to worry about pg_dump, as opclass
> parameters are loaded with CREATE INDEX.

By the way, while looking at this area of the code (particularly
tsvector and gist), I was under the impression that it is safe to
assume that we don't particularly need to rebuild the index when
changing its attoptions this way, but I have also the feeling to be
rather naive here.

Alexander, you have much more experience in this area than I do, what
are your thoughts on the matter?

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo NAGATA 2021-10-29 09:16:28 Re: Implementing Incremental View Maintenance
Previous Message Amit Kapila 2021-10-29 09:02:29 Re: Skipping logical replication transactions on subscriber side