Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Дата
Msg-id CAB7nPqR=jHB2Eh0r6bjcExsU_qkdWFyo23coxBt325aHmcSiuw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()  (David Rowley <david.rowley@2ndquadrant.com>)
Ответы Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()
Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Список pgsql-hackers
Дерево обсуждения 
On Wed, Apr 19, 2017 at 12:36 PM, David Rowley
<david.rowley@2ndquadrant.com> wrote:
> In favour of "location" -> "lsn": Tom, Stephen, David Steel
> In favour of "lsn" -> "location": Peter, Kyotaro

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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: David Rowley
Дата:
Сообщение: [HACKERS] Fixup some misusage of appendStringInfo and friends
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: [HACKERS] Quorum commit for multiple synchronous replication.