From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Vadim Mikheev'" <vmikheev(at)sectorbase(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | AW: RE: xlog loose ends, continued |
Date: | 2001-03-13 16:14:57 |
Message-ID: | 11C1E6749A55D411A9670001FA687963368248@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > Anyway I like idea of StartUpID in page headers - this will help
> >
> > Can you please describe StartUpID for me ?
> > Ideal would be a stamp that has the last (smallest open) XID, or something else
> > that has more or less timestamp characteristics (without the actual need of wallclock)
> > in regard to the WAL.
>
> StartUpID counts database startups and so has timestamp characteristics.
> Actually, idea is to use SUI in future to allow reusing XIDs after startup: seeing
> old SUI in data pages we'll know that all transaction on this page was committed
> "long ago" (ie visible from MVCC POV). This requires UNDO, of course.
First thanx for the description, but db startup would only count to 5-7 per year :-),
is that sufficient ? It hardly sounds like anything useful to include in page header.
What about the xlog id, that is also used for xlog file name, but I still think a xid would
be the best candidate.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Marsden | 2001-03-13 16:31:33 | Re: problem with fe/be protocol and large objects |
Previous Message | Bruce Momjian | 2001-03-13 16:04:25 | Re: Performance monitor |