> > > It will be sufficient if DB will not use all 2^32 XIDs
> > > without shutdown.
> >
> > I liked the xid wraparound idea, won't that be sufficient here too ?
> > I don't like the idea to reuse a xid sooner than absolutely necessary.
>
> We need it to reduce pg_log size requirements.
Yes,
> > > 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 P
> > > 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
>wallcl
> 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
