From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Mike Tamburro <m(dot)tamburro(at)technologue(dot)com> |
Cc: | pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: Wrap-around XID's |
Date: | 2005-02-08 22:15:29 |
Message-ID: | 42093A01.9000804@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
> What I need:
>
> 1) More detail on the use of XID's by PostgreSQL, so I can better
> understand the problem.
The problem is a phantom as long as you perform routine vacuuming. This
is something you have to do anyway so it isn't that big of a deal.
> 2) An explanation that the work-around is sufficient.
Just vacuum :)
>
> 3) I see that PostgreSQL has an 8-byte data type (bigint) which would
> all but the solve the problem. Are there any plans to offer 8-byte XID's
> in future versions of PostgreSQL?
I don't know about the 8-byte xid but again, as long as you vacuum it
isn't an issue.
Sincerely,
Joshua D. Drake
>
> Thank you very much for your help,
>
>
>
> -------
> Michael Tamburro
> Director, Information Technology Department
> Technologue, Inc.
> www.technologue.com
> 610-430-0104 x29
>
--
Command Prompt, Inc., your source for PostgreSQL replication,
professional support, programming, managed services, shared
and dedicated hosting. Home of the Open Source Projects plPHP,
plPerlNG, pgManage, and pgPHPtoolkit.
Contact us now at: +1-503-667-4564 - http://www.commandprompt.com
Attachment | Content-Type | Size |
---|---|---|
jd.vcf | text/x-vcard | 640 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2005-02-08 23:34:01 | Re: Wrap-around XID's |
Previous Message | Mike Tamburro | 2005-02-08 21:56:12 | Wrap-around XID's |