Re: pg_lsn cast to/from int8 - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pg_lsn cast to/from int8
Date
Msg-id CABUevEzRctu_BZNG1XcHtoLe6qY5zDP5GdyJD0Vjaw3BEArN1g@mail.gmail.com
Whole thread Raw
In response to Re: pg_lsn cast to/from int8  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers


On Tue, Jan 26, 2016 at 4:58 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
On 26 January 2016 at 22:07, Magnus Hagander <magnus@hagander.net> wrote:
 
In this case, mostly legacy compatibility. Making an app that works with versions that don't have pg_lsn have a nice path forward to the modern world. Being able to cast from pg_lsn to int8 can also make it easier to work with the values in the client application, though I don't need that for this particular one.


Wouldn't we need a uint8 type for that?

I guess we could just show people negative LSNs if the high bit is set (that being rather unlikely) but still... 


Yes, in theory. Though the likelihood of actually reaching that... It would probably be OK to just throw an error if the high bit is actually set.

--

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: PL/Pythonu - function ereport
Next
From: Robert Haas
Date:
Subject: Re: Relation extension scalability