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

From Euler Taveira
Subject Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Date
Msg-id CAHE3wgh8ikgHW-vhbX9mTje1cQP13PNZvHUFmWg=rVutjk0cRw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
List 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

pgsql-hackers by date:

Previous
From: Mark Rofail
Date:
Subject: Fwd: [HACKERS] GSoC 2017 Proposal
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher