On Thu, Jul 7, 2011 at 2:55 PM, Noah Misch <n...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
