Postgres Pro
Downloads
Home   >   mailing lists

Re: How to avoid transaction ID wrap - Mailing list pgsql-hackers

From Tom Lane
Subject Re: How to avoid transaction ID wrap
Date
Msg-id 475.1149695265@sss.pgh.pa.us
Whole thread Raw
In response to Re: How to avoid transaction ID wrap  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: How to avoid transaction ID wrap  ("Jim C. Nasby" <jnasby@pervasive.com>)
Re: How to avoid transaction ID wrap  (Koichi Suzuki <suzuki.koichi@oss.ntt.co.jp>)
List pgsql-hackers
Tree view 
Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes:
> Koichi Suzuki wrote:
>> I've once proposed a patch for 64bit transaction ID, but this causes 
>> some overhead to each tuple (XMIN and XMAX).

> Did you check performance on 32-bit or 64-bit systems and 64-bit binary 
> version of PGSQL? I think that today is not problem to have 64-bit 
> architecture and 64-bit ID should increase scalability of Postgres.

The percentage increase in I/O demand is the main reason the patch was
rejected, not so much the arithmetic.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: self-deadlock at FATAL exit of boostrap process on read error
Next
From: Teodor Sigaev
Date:
Subject: Proposal to improve multicolumn GiST page split algoriithm.