From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Single pass vacuum - take 1 |
Date: | 2011-07-14 18:43:53 |
Message-ID: | 1310668936-sup-1775@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Pavan Deolasee's message of jue jul 14 13:54:36 -0400 2011:
> On Thu, Jul 14, 2011 at 12:43 PM, Heikki Linnakangas <
> heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> > Seems odd to store relindxvacxlogid/off as two int32 columns. Store it in
> > one uint64 column, or invent a new datatype for LSNs, or store it as text in
> > %X/%X format.
> >
> >
> Yeah. I don't remember what issues I faced with uint64 column, may be did
> not get around the case where uint64 is not natively supported on the
> platform. But %X/%X looks very reasonable. Will change to that.
Where is this to be stored?
AFAIR we no longer support platforms that do not have working 64 bit
integer types.
As a column name, relindxvacxlogid seems a bit unfortunate, BTW ...
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-07-14 18:54:28 | Re: Allow pg_archivecleanup to ignore extensions |
Previous Message | Florian Pflug | 2011-07-14 18:43:13 | Re: Need help understanding pg_locks |