Hannu Krosing wrote:
> I don't think it is a good idea to store xid's anywhere but in xmin/xmax
> columns, as doing so would cause nasty xid wraparound problems.
> Instead you should wait, after completeing the index , for all
> concurrent transactions to end before you mark the index as "usable for
> queries", similar to the way CREATE INDEX CONCURRENTLY does.

We already discussed having VACUUM FREEZE deal with the pg_index xid
column.  I don't see how having CREATE INDEX wait for all completed
transactions helps us from a usability perspective.

  Bruce Momjian  <[EMAIL PROTECTED]>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to