Postgres Pro
Downloads
Home   >   mailing lists

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

From Peter Eisentraut
Subject Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()
Date
Msg-id 54d1d5fc-a8aa-b687-0d65-bd488d0e48ba@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On 4/14/17 11:36, Bruce Momjian wrote:
> Yeah, this area is complex enough so any consistency we can add helps.

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"?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: [HACKERS] minor typo in client-auth.sgml
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()