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-qGvwBuPOS1UBfjHZ-o+PY4R=OROLkKiuFO9dC3MnWog@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn() (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
|
| Список | pgsql-hackers |
On 19 April 2017 at 15:31, Tom Lane <tgl@sss.pgh.pa.us> wrote: > David Rowley <david.rowley@2ndquadrant.com> writes: >> OK, so I've read over this thread again and I think it's time to >> summarise the votes: >> ... >> In favour of "location" -> "lsn": Stephen, David Steel, >> In favour of "lsn" -> "location": Peter, Tom, Kyotaro > > FWIW, I was not voting in favor of "location"; I was just saying that > I wanted consistency. If we're voting which way to move, please count > me as a vote for "lsn". Updated votes: In favour of "location" -> "lsn": Tom, Stephen, David Steel In favour of "lsn" -> "location": Peter, Kyotaro -- David Rowley http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: