Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn() - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()
Date
Msg-id 20170419.173024.248689294.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
At Wed, 19 Apr 2017 13:32:48 +0900, Michael Paquier <michael.paquier@gmail.com> wrote in
<CAB7nPqR=jHB2Eh0r6bjcExsU_qkdWFyo23coxBt325aHmcSiuw@mail.gmail.com>
> On Wed, Apr 19, 2017 at 12:36 PM, David Rowley
> <david.rowley@2ndquadrant.com> wrote:
> > In favour of "location" -> "lsn": Tom, Stephen, David Steel
> > In favour of "lsn" -> "location": Peter, Kyotaro
> 
> I vote for "location" -> "lsn". I would expect complains about the
> current inconsistency at some point, and the function names have been
> already changed for this release..

I won't stick on "location" except that "pg_wal_lsn_diff" seems
no longer useful.

regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] some review comments on logical rep code
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] some review comments on logical rep code