Re: pg_lsn cast to/from int8

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_lsn cast to/from int8
Date: 2016-02-02 14:56:18
Message-ID: CABUevEzRctu_BZNG1XcHtoLe6qY5zDP5GdyJD0Vjaw3BEArN1g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 26, 2016 at 4:58 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:

> On 26 January 2016 at 22:07, Magnus Hagander <magnus(at)hagander(dot)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.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-02-02 15:12:38 Re: Relation extension scalability
Previous Message Jim Nasby 2016-02-02 14:52:02 Re: Add links to commit fests to patch summary page