Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()
Дата
Msg-id 54d1d5fc-a8aa-b687-0d65-bd488d0e48ba@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Список pgsql-hackers
Дерево обсуждения 
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 по дате отправления:

Предыдущее
От: Jaime Casanova
Дата:
Сообщение: [HACKERS] minor typo in client-auth.sgml
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()