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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Дата
Msg-id 19052.1492210333@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Список pgsql-hackers
Дерево обсуждения 
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> 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"?

I wouldn't object to standardizing on "location" instead of "lsn" in the
related function and column names.  What I don't like is using different
words for the same thing.
        regards, tom lane

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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] Should pg_current_wal_location() becomepg_current_wal_lsn()
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] minor typo in client-auth.sgml