From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: xlog location arithmetic |
Date: | 2011-12-23 16:15:07 |
Message-ID: | CA+Tgmob1kiVeH13Z4jVRZCMnK2ZZshZd-encd1_oS4Yb9JzZ3w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 23, 2011 at 10:59 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Fri, Dec 23, 2011 at 10:18 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Even if there are several, what exact advantage does a datatype offer
>>> over representing LSN values as numerics? It seems to me to be adding
>>> complication and extra code (I/O converters at least) for very little
>>> gain.
>
>> I guess I'm just constitutionally averse to labeling things as "text"
>> when they really aren't.
>
> Er ... text? I thought the proposal was to use numeric.
The proposal is to make a function that takes a text argument (which
is really an LSN, but we choose to represent it as text) and returns
numeric.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-12-23 16:35:43 | Re: WIP: explain analyze with 'rows' but not timing |
Previous Message | Kevin Grittner | 2011-12-23 16:14:06 | Re: Page Checksums + Double Writes |