Re: pg_dump and XID limit

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Elliot Chance <elliotchance(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dump and XID limit
Date: 2010-11-24 15:16:48
Message-ID: 18330.1290611808@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Elliot Chance <elliotchance(at)gmail(dot)com> writes:
> Wouldn't that mean at some point it would be advisable to be using 64bit transaction IDs? Or would that change too much of the codebase?

It's not so much "too much of the codebase" as "nobody wants another 8
bytes added to per-row overhead". Holding a transaction open for
circa 2G transactions would be disastrous anyway, because of table bloat
from inability to reclaim dead rows.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message James Cloos 2010-11-24 20:59:30 Re: binary logs: a location other than pg_xlog??
Previous Message Kevin Grittner 2010-11-24 14:54:20 Re: pg_dump and XID limit