Request a Demo
Home   >   mailing lists

Re: should we add a XLogRecPtr/LSN SQL type? - Mailing list pgsql-hackers

From Greg Stark
Subject Re: should we add a XLogRecPtr/LSN SQL type?
Date
Msg-id CAM-w4HPvZFcj5P70AHTxaYgx_oxTz2LTGVw8c4GirS41szfFsA@mail.gmail.com
Whole thread Raw
In response to should we add a XLogRecPtr/LSN SQL type?  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Tree view

Bonus points if you implement a (explicit) cast to and from timestamptz :)

--
greg

On 11 Dec 2013 12:41, "Andres Freund" <andres@2ndquadrant.com> wrote:
Hi,

There's already a couple of SQL function dealing with XLogRecPtrs and
the logical replication work will add a couple of more. Currently each
of those funtions taking/returning an LSN does sprintf/scanf to
print/parse the strings. Which both is awkward and potentially
noticeable performancewise.

It seems relatively simple to add a proper type, with implicit casts
from text, instead?

Greetings,

Andres Freund

--
 Andres Freund                     http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Rajeev rastogi
Date:
Subject: Re: TODO: Split out pg_resetxlog output into pre- and post-sections
Next
From: KONDO Mitsumasa
Date:
Subject: Re: Time-Delayed Standbys