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

From James Coleman
Subject Re: Correct docs re: rewriting indexes when table rewrite is skipped
Date
Msg-id CAAaqYe-QKZOMU+TJ9HJTxN=hz4VdcuDWaEOA09SwbXuBK+H8NA@mail.gmail.com
Whole thread Raw
In response to Re: Correct docs re: rewriting indexes when table rewrite is skipped  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Correct docs re: rewriting indexes when table rewrite is skipped  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Mar 31, 2022 at 10:29 AM Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Thu, Mar 31, 2022 at 10:14 AM James Coleman <jtc331@gmail.com> wrote:
> > Is the attached more along the lines of what you were thinking?
>
> Yeah. Maybe this would be a little clearer: "For example, if the
> collation for a column has been changed, an index rebuild is always
> required, because the new sort order might be different. However, in
> the absence of a collation change, a column can be changed from text
> to varchar or vice versa without rebuilding the indexes, because these
> data types sort identically."

Updated.

> We don't seem to be very consistent about whether we write type names
> like VARCHAR in upper case or lower case in the documentation. I'd
> vote for using lower-case, but it probably doesn't matter much.

Grepping suggests lower case is more common (2 to 1) so I switched to
that. Interestingly for "text" it's 700+ to 1 :)

Thanks,
James Coleman

Attachment

pgsql-hackers by date:

Previous
From: Devrim Gündüz
Date:
Subject: Re: head fails to build on SLES 12
Next
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Add 'basebackup_to_shell' contrib module.