| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, furuyao(at)pm(dot)nttdata(dot)co(dot)jp, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, teranishih(at)nttdata(dot)co(dot)jp |
| Subject: | Re: PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog. |
| Date: | 2014-11-17 03:30:12 |
| Message-ID: | CAB7nPqS66T_xaBo1SraTDCR0wOBdzC7WhkuL_r8JeotseyPgsQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 17, 2014 at 10:02 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Sat, Nov 15, 2014 at 9:10 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)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 | Content-Type | Size |
|---|---|---|
| 20141117_pg_receivexlog_flush_ptr.patch | text/x-patch | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2014-11-17 04:13:22 | Re: BRIN indexes - TRAP: BadArgument |
| Previous Message | Dilip kumar | 2014-11-17 03:25:42 | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |