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 19052.1492210333@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> If we're talking about making things easier to understand, wouldn't a
> random user rather know what a WAL "location" is instead of a WAL "LSN"?

I wouldn't object to standardizing on "location" instead of "lsn" in the
related function and column names.  What I don't like is using different
words for the same thing.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] minor typo in client-auth.sgml