Re: concerns around pg_lsn - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: concerns around pg_lsn
Date
Msg-id CAMsr+YFaUxehLvxM_VyK=hoEY5OUO_RySjeNcmGBBHD4gSG7nA@mail.gmail.com
Whole thread Raw
In response to Re: concerns around pg_lsn  (Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>)
List pgsql-hackers
On the topic of pg_lsn, I recently noticed that there's no operator(+)(pg_lsn,bigint) nor is there an operator(-)(pg_lsn,bigint) so you can't compute offsets easily. We don't have a cast between pg_lsn and bigint because we don't expose an unsigned bigint type in SQL, so you can't work around it that way.

I may be missing the obvious, but I suggest (and will follow with a patch for) adding + and - operators for computing offsets. I was considering an age() function for it too, but I think it's best to force the user to be clear about what current LSN they want to compare with so I'll skip that.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 2ndQuadrant - PostgreSQL Solutions for the Enterprise

pgsql-hackers by date:

Previous
From: Ian Barwick
Date:
Subject: Re: [PATCH] minor bugfix for pg_basebackup (9.6 ~ )
Next
From: Craig Ringer
Date:
Subject: Re: Global temporary tables