Re: Correct docs re: rewriting indexes when table rewrite is skipped - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Correct docs re: rewriting indexes when table rewrite is skipped
Date
Msg-id CA+Tgmobsekq+FHMQ-Zc5KDOFxUTgVunVB33JMWzLtn3CKa4AZA@mail.gmail.com
Whole thread Raw
In response to Re: Correct docs re: rewriting indexes when table rewrite is skipped  (James Coleman <jtc331@gmail.com>)
Responses Re: Correct docs re: rewriting indexes when table rewrite is skipped  (James Coleman <jtc331@gmail.com>)
List pgsql-hackers
On Wed, Mar 30, 2022 at 4:33 PM James Coleman <jtc331@gmail.com> wrote:
> Hmm, having it match the way it works makes sense. Would you feel
> comfortable with an intermediate step (queueing up that as a larger
> change) changing the clause to something like "indexes will still have
> to be rebuilt unless the system can guarantee that the sort order is
> proven to be unchanged" (with appropriate wordsmithing to be a bit
> less verbose if possible)?

Yeah, that seems fine. It's arguable how much detail we should go into
here - but a statement of the form you propose is not misleading, and
that's what seems most important to me.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: [Proposal] vacuumdb --schema only
Next
From: Robert Haas
Date:
Subject: Re: pgsql: Add 'basebackup_to_shell' contrib module.