Horton

Re: Should pg_current_wal_location() become pg_current_wal_lsn()

Euler Taveira <euler@timbira.com.br>

View thread View on postgr.es
From: Euler Taveira <euler@timbira.com.br>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, David Steele <david@pgmasters.net>, Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-04-19T19:29:22Z
Lists: pgsql-hackers 
2017-04-19 1:32 GMT-03:00 Michael Paquier <michael.paquier@gmail.com>:

> 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..
>

+1.


-- 
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>

Commits

  1. Rename WAL-related functions and views to use "lsn" not "location".