Re: Avoid index rebuilds for no-rewrite ALTER TABLE ALTER TYPE
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Noah Misch <noah@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2011-07-07T19:06:46Z
Lists: pgsql-hackers
On Thu, Jul 7, 2011 at 2:55 PM, Noah Misch <noah@2ndquadrant.com> wrote: > CheckIndexCompatible() calls ComputeIndexAttrs() to resolve the new operator > classes, collations and exclusion operators for each index column. It then > checks those against the existing values for the same. I figured that was > obvious enough, but do you want a new version noting that? I guess one question I had was... are we depending on the fact that ComputeIndexAttrs() performs a bunch of internal sanity checks? Or are we just expecting those to always pass, and we're going to examine the outputs after the fact? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company