RE: Transaction ID wraparound: problem and proposed sol ution - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: Transaction ID wraparound: problem and proposed sol ution
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D314A@sectorbase1.sectorbase.com
Whole thread Raw
List pgsql-hackers
> > OK, 2^64 isn't mathematically unbounded, but let's see you 
> > buy a disk that will hold it ;-).  My point is that if we want
> > to think about allowing >4G transactions, part of the answer
> > has to be a way to recycle pg_log space. Otherwise it's still
> > not really practical.
> 
> I kind of like vadim's idea of segmenting pg_log. 
> 
> Segments in which all the xacts have been commited could be deleted.

Without undo we have to ensure that all tables are vacuumed after
all transactions related to a segment were committed/aborted.

Vadim


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: problems with configure
Next
From: Hiroshi Inoue
Date:
Subject: Re: ResetSystemCaches(was Re: relation ### modified while in use)