Re: Should pg_current_wal_location() become pg_current_wal_lsn()

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Steele <david(at)pgmasters(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should pg_current_wal_location() become pg_current_wal_lsn()
Date: 2017-04-19 19:29:22
Message-ID: CAHE3wgh8ikgHW-vhbX9mTje1cQP13PNZvHUFmWg=rVutjk0cRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2017-04-19 1:32 GMT-03:00 Michael Paquier <michael(dot)paquier(at)gmail(dot)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>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-04-19 19:57:35 Re: logical replication and PANIC during shutdown checkpoint in publisher
Previous Message Mark Rofail 2017-04-19 19:28:46 Fwd: GSoC 2017 Proposal