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+TgmoZeOZ-FPXeGvZFuZA2+4=yDYL+bx2B1E0R_yS9=7p5arQ@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
List pgsql-hackers
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."

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.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: head fails to build on SLES 12
Next
From: Aleksander Alekseev
Date:
Subject: Unit tests for SLRU