"Pavan Deolasee" <pavan.deolasee@gmail.com> writes:
> On 3/26/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Hmm ... actually, CREATE INDEX CONCURRENTLY gets this wrong already, no?
> Yes, C.I.C gets it wrong. I confirmed that new index is seen as invalid
> for existing sessions. Is it something we should fix ?
Certainly.
It might be feasible to have RelationReloadClassinfo re-read the
pg_index row and apply only the updates for specific known-changeable
columns. The stuff it's worried about is the subsidiary data such
as support function fmgr lookup records, but we don't need those to
change on the fly.
regards, tom lane