Re: Support for REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Support for REINDEX CONCURRENTLY
Date
Msg-id CAB7nPqTNWS=c12ZgTwxL0zzY8prtjqQMWy89_0Bm5YdFhhDvcA@mail.gmail.com
Whole thread Raw
In response to Re: Support for REINDEX CONCURRENTLY  (Jim Nasby <jim@nasby.net>)
List pgsql-hackers


On Tue, Oct 9, 2012 at 8:14 AM, Jim Nasby <jim@nasby.net> wrote:
Hrm... the claim was made that everything relating to the index, including pg_depend and pg_contstraint, got duplicated. But I don't know how you could duplicate a constraint without also playing name games. Perhaps name games are being played there as well...
Yes, it is what was originally intended. Please note the pg_constraint entry was not duplicated correctly in the first version of the patch because of a bug I already fixed.
I will provide another version soon if necessary.
 

 
Right now I don't see anything that would make switching oids easier than
relfilenodes.

Yeah... in order to make either of those schemes work I think there would need to non-trivial internal changes so that we weren't just passing around raw OIDs/filenodes.

BTW, it occurs to me that this problem might be easier to deal with if we had support for accessing the catalog with the same snapshot as the main query was using... IIRC that's been discussed in the past for other issues.
Yes, it would be better and helpful to have such a mechanism even for other operations.
--
Michael Paquier
http://michael.otacoo.com

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Support for REINDEX CONCURRENTLY
Next
From: Joachim Wieland
Date:
Subject: Re: Add FET to Default and Europe.txt