Postgres Pro
Downloads
Home   >   mailing lists

Re: PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.
Date
Msg-id CAB7nPqS66T_xaBo1SraTDCR0wOBdzC7WhkuL_r8JeotseyPgsQ@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Tree view 
On Mon, Nov 17, 2014 at 10:02 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Sat, Nov 15, 2014 at 9:10 PM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
>> Yep, sounds a good thing to do if master requested answer from the
>> client in the keepalive message. Something like the patch attached
>> would make the deal.
>
> Isn't it better to do this only when replication slot is used?
Makes sense. What about a check using reportFlushPosition then?
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Dilip kumar
Date:
Subject: Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ]
Next
From: Amit Kapila
Date:
Subject: Re: BRIN indexes - TRAP: BadArgument