From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Mikko Partio <mpartio@gmail.com>
Cc: Pallav Kalva <pkalva@livedatagroup.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 8.2 Autovacuum BUG ?
Date: Fri, 31 Aug 2007 15:08:45 -0400
Message-ID: <247.1188587325@sss.pgh.pa.us> (raw)
In-Reply-To: <20070831184744.GK8046@alvh.no-ip.org>
References: <46D83427.60001@livedatagroup.com>
<25038.1188574775@sss.pgh.pa.us>
<46D83C50.3040409@livedatagroup.com>
<20070831161158.GD8046@alvh.no-ip.org>
<2ca799770708311131r5ae5e3eera66a7cea1fc5917d@mail.gmail.com>
<20070831184744.GK8046@alvh.no-ip.org>
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Mikko Partio escribió:
>> Off-topic question: the documentation says that XID numbers are 32 bit.
>> Could the XID be 64 bit when running on a 64 bit platform? That would
>> effectively prevent wrap-around issues.
> No, because they would take too much space in tuple headers.
It's worth noting that the patch Florian is working on, to suppress
assignment of XIDs for transactions that never write anything, will make
for a large reduction in the rate of XID consumption in many real-world
applications. That will reduce the need for tuple freezing and probably
lessen the attraction of wider XIDs even more.
If he gets it done soon (before the HOT dust settles) I will be strongly
tempted to try to sneak it into 8.3 ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@commandprompt.com, mpartio@gmail.com, pkalva@livedatagroup.com
Subject: Re: 8.2 Autovacuum BUG ?
In-Reply-To: <247.1188587325@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox