Re: should we add a XLogRecPtr/LSN SQL type?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: should we add a XLogRecPtr/LSN SQL type?
Date: 2014-02-19 17:47:40
Message-ID: CA+TgmoYwzQarFcyF-tNNQUy_-rXuFzL=ReB9gn=uLvNJrC8jnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 5, 2014 at 9:26 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Thu, Feb 6, 2014 at 3:48 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> On 2/5/14, 1:31 PM, Robert Haas wrote:
>>> On Tue, Feb 4, 2014 at 3:26 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>>>> Perhaps this type should be called pglsn, since it's an
>>>> implementation-specific detail and not a universal concept like int,
>>>> point, or uuid.
>>>
>>> If we're going to do that, I suggest pg_lsn rather than pglsn. We
>>> already have pg_node_tree, so using underscores for separation would
>>> be more consistent.
>>
>> Yes, that's a good precedent in multiple ways.
> Here are updated patches to use pg_lsn instead of pglsn...

OK, so I think this stuff is all committed now, with assorted changes.
Thanks for your work on this.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-02-19 18:01:02 Re: Changeset Extraction v7.6.1
Previous Message Robert Haas 2014-02-19 17:35:16 Re: [bug fix] "pg_ctl stop" times out when it should respond quickly