| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| 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-01-26 15:58:21 |
| Message-ID: | CAMsr+YGGh+FMY1jUcMHWmsvLTB9rjTRUJ6eaRE1A++h-Gd81wQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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...
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-01-26 16:09:13 | Re: WIP: Failover Slots |
| Previous Message | Simon Riggs | 2016-01-26 15:56:12 | Re: remove wal_level archive |