Re: CREATE INDEX and HOT - revised design

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Hannu Krosing <hannu(at)skype(dot)net>, 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:45:53
Message-ID: 200703231345.l2NDjrW21353@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavan Deolasee wrote:
> > Xids are unstable and will come back to bite you after 2G transactions.
> >
> > Why not just use the "isindvalid" flag ?
> >
> >
> Who would set the flag to true ? Unless of course we are waiting in
> CREATE INDEX. But that seems to be less acceptable to me.

Agreed, and we have the problem of crash recovery if we do that. The
xid seems to handle that automatically.

--
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. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hugh Sasse 2007-03-23 14:15:12 Documentation access problems.
Previous Message Zoltan Boszormenyi 2007-03-23 13:45:12 Crash bug in 8.2.3 on Solaris 10/Sparc