Re: SYSTEM_IDENTIFY fields was:(Re: [COMMITTERS] pgsql: Include more status information in walsender results)

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: SYSTEM_IDENTIFY fields was:(Re: [COMMITTERS] pgsql: Include more status information in walsender results)
Дата
Msg-id BANLkTina-JosSV-d25DsO=xeu_GaAr+7fA@mail.gmail.com
обсуждение исходный текст
Ответ на SYSTEM_IDENTIFY fields was:(Re: [COMMITTERS] pgsql: Include more status information in walsender results)  (Jaime Casanova <jaime@2ndquadrant.com>)
Список pgsql-hackers
On Sat, Apr 30, 2011 at 03:13, Jaime Casanova <jaime@2ndquadrant.com> wrote:
> On Thu, Feb 3, 2011 at 7:56 AM, Magnus Hagander <magnus@hagander.net> wrote:
>> Include more status information in walsender results
>>
>> Add the current xlog insert location to the response of
>> IDENTIFY_SYSTEM
>
> why was this third field added to SYSTEM_IDENTIFY? can't find any
> place where it's used...
> not even on BaseBackup() before the call to SYSTEM_IDENTIFY was removed

I believe this was discussed before the patch was committed, but here
is the short version: It is required for the streaming client. It
didn't make it into 9.1, but given that it's a very useful tool
outside it, I think we should still keep the functionality in the
server.

Prior to this, that client required two separate logins, once to get
the current xlog location and then another one to do the streaming.
With this, the information is available over the streaming protocol
alone.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Proposed patch: Smooth replication during VACUUM FULL
Следующее
От: David Fetter
Дата:
Сообщение: Re: HTML tags :/