| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)skype(dot)net> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Pavan Deolasee <pavan(dot)deolasee(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: CREATE INDEX and HOT - revised design |
| Date: | 2007-03-23 13:44:32 |
| Message-ID: | 200703231344.l2NDiWd21121@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltan Boszormenyi | 2007-03-23 13:45:12 | Crash bug in 8.2.3 on Solaris 10/Sparc |
| Previous Message | Florian G. Pflug | 2007-03-23 13:04:29 | Re: CREATE INDEX and HOT - revised design |