Hannu Krosing <[EMAIL PROTECTED]> writes: >> * disk space --- letting pg_log grow without bound isn't a pleasant >> prospect either. > How will 2x size increase of xid cause "boundless" growth of pg_log ;) 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. regards, tom lane
- Re: [HACKERS] Transaction ID wraparound: pro... Nathan Myers
- Re: [HACKERS] Transaction ID wraparound: problem and prop... Bruce Momjian
- Re: [HACKERS] Transaction ID wraparound: problem and... Vadim Mikheev
- Re: [HACKERS] Transaction ID wraparound: problem and prop... Hannu Krosing
- Re: [HACKERS] Transaction ID wraparound: problem and... Peter Eisentraut
- Re: [HACKERS] Transaction ID wraparound: problem... Larry Rosenman
- Re: [HACKERS] Transaction ID wraparound: pro... Tom Lane
- Re: [HACKERS] Transaction ID wraparound:... Larry Rosenman
- Re: [HACKERS] Transaction ID wraparound: problem... Hannu Krosing
- Re: [HACKERS] Transaction ID wraparound: pro... Larry Rosenman
- Re: [HACKERS] Transaction ID wraparound: problem and... Tom Lane
- Re: [HACKERS] Transaction ID wraparound: problem... Mark Hollomon
- Re: [HACKERS] Transaction ID wraparound: problem and prop... Bruce Momjian
- RE: [HACKERS] Transaction ID wraparound: problem and prop... Mikheev, Vadim
- RE: [HACKERS] Transaction ID wraparound: problem and prop... Mikheev, Vadim