Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Date
Msg-id 9012.1492572667@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-hackers
Tree view 
David Rowley <david.rowley@2ndquadrant.com> writes:
> OK, so I've read over this thread again and I think it's time to
> summarise the votes:
> ...
> In favour of "location" -> "lsn": Stephen, David Steel,
> In favour of "lsn" -> "location": Peter, Tom, Kyotaro

FWIW, I was not voting in favor of "location"; I was just saying that
I wanted consistency.  If we're voting which way to move, please count
me as a vote for "lsn".
        regards, tom lane

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Inadequate parallel-safety check for SubPlans
Next
From: Noah Misch
Date:
Subject: Re: [HACKERS] Quorum commit for multiple synchronous replication.