Re: Unique transaction ID

From: Jaime Casanova <systemguards(at)gmail(dot)com>
To: Robert Osowiecki <robson(at)cavern(dot)pl>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Unique transaction ID
Date: 2006-01-04 19:24:14
Message-ID: c2d9e70e0601041124p2c5b290qae1d6685682a15a6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/4/06, Robert Osowiecki <robson(at)cavern(dot)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 ;)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-01-04 19:36:12 Re: copy from error
Previous Message Michelle Konzack 2006-01-04 18:52:43 "REFERENCES" and UNIQUE