Re: Unique transaction ID - Mailing list pgsql-general

From Jaime Casanova
Subject Re: Unique transaction ID
Date
Msg-id c2d9e70e0601041124p2c5b290qae1d6685682a15a6@mail.gmail.com
Whole thread Raw
In response to Re: Unique transaction ID  (Robert Osowiecki <robson@cavern.pl>)
List pgsql-general
On 1/4/06, Robert Osowiecki <robson@cavern.pl> wrote:
> Jaime Casanova napisał(a):
>
> > it exists a transaction id called XID, you can't get it via sql
> >
> >though, you need to make a c function and invoke GetTopTransactionId()
> >(or GetCurrentTransactionId() in versions prior to 8.0)
> >
> >
> I've read a little about problems with overlapping XID and how they were
> resolved. I don't understand everything but it seems that XID could be
> decreased after vacuum, could it?
>
> Robson.
>
>

NO!!!

if for overlapping you are refering to the wraparound problem you just
have to execute VACUUM at least every billion transactions or if you
are in 8.1.x let autovaccum keep you safe...

http://www.postgresql.org/docs/current/static/maintenance.html#VACUUM-FOR-WRAPAROUND

--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)

pgsql-general by date:

Previous
From: Robert Osowiecki
Date:
Subject: Re: Unique transaction ID
Next
From: Tom Lane
Date:
Subject: Re: copy from error