Re: Transaction ID wraparound: problem and proposed solution

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction ID wraparound: problem and proposed solution
Date: 2000-11-05 18:02:37
Message-ID: 788.973447357@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing <hannu(at)tm(dot)ee> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-05 18:07:12 Re: Transaction ID wraparound: problem and proposed solution
Previous Message Peter Eisentraut 2000-11-05 15:42:33 Re: Transaction ID wraparound: problem and proposed solution