Re: Correct docs re: rewriting indexes when table rewrite is skipped
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: James Coleman <jtc331@gmail.com>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-03-31T14:28:45Z
Lists: 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
Commits
-
docs: Changing column type doesn't always require an index rebuild.
- fa25bebb827a 15.0 landed