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

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Дата
Msg-id CAKJS1f_fcD3LXoUhiuPz0eWuDOLf296kxvZ=DpiBbMiznqx3Ug@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() become pg_current_wal_lsn()  (Noah Misch <noah@leadboat.com>)
Список pgsql-hackers
On 2 May 2017 at 00:10, David Rowley <david.rowley@2ndquadrant.com> wrote:
> On 20 April 2017 at 07:29, Euler Taveira <euler@timbira.com.br> wrote:
>> 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..
>
> OK, so I've created a draft patch which does this.

I ended up adding this to the open items list.  I feel it's best to be
on there so that we don't forget about this.

If we decide not to do it then we can just remove it from the list,
but it would be a shame to release the beta having forgotten to make
this change.

Do any of the committers who voted for this change feel inclined to
pick this patch up?

-- David Rowley                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



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

Предыдущее
От: Serge Rielau
Дата:
Сообщение: Re: [HACKERS] CTE inlining
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] CTE inlining