Re: [HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-19 Thread Fujii Masao
On Wed, Nov 19, 2014 at 5:15 PM, Magnus Hagander wrote: > On Wed, Nov 19, 2014 at 6:16 AM, Fujii Masao wrote: >> On Mon, Nov 17, 2014 at 12:30 PM, Michael Paquier >> wrote: >>> On Mon, Nov 17, 2014 at 10:02 AM, Fujii Masao wrote: On Sat, Nov 15, 2014 at 9:10 PM, Michael Paquier wrote

Re: [HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-19 Thread Magnus Hagander
On Wed, Nov 19, 2014 at 6:16 AM, Fujii Masao wrote: > On Mon, Nov 17, 2014 at 12:30 PM, Michael Paquier > wrote: >> On Mon, Nov 17, 2014 at 10:02 AM, Fujii Masao wrote: >>> On Sat, Nov 15, 2014 at 9:10 PM, Michael Paquier >>> wrote: Yep, sounds a good thing to do if master requested answer

Re: [HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-18 Thread Fujii Masao
On Mon, Nov 17, 2014 at 12:30 PM, Michael Paquier wrote: > On Mon, Nov 17, 2014 at 10:02 AM, Fujii Masao wrote: >> On Sat, Nov 15, 2014 at 9:10 PM, Michael Paquier >> wrote: >>> Yep, sounds a good thing to do if master requested answer from the >>> client in the keepalive message. Something like

Re: [HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-16 Thread Michael Paquier
On Mon, Nov 17, 2014 at 10:02 AM, Fujii Masao wrote: > On Sat, Nov 15, 2014 at 9:10 PM, Michael Paquier > 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

Re: [HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-16 Thread Fujii Masao
On Sat, Nov 15, 2014 at 9:10 PM, Michael Paquier wrote: > On Sat, Nov 15, 2014 at 3:42 AM, Andres Freund wrote: >> On 2014-11-15 03:25:16 +0900, Fujii Masao wrote: >>> On Fri, Nov 14, 2014 at 7:22 PM, wrote: >>> > "pg_ctl stop" does't work propley, if --slot option is specified when WAL >>> >

Re: [HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-15 Thread Michael Paquier
On Sat, Nov 15, 2014 at 3:42 AM, Andres Freund wrote: > On 2014-11-15 03:25:16 +0900, Fujii Masao wrote: >> On Fri, Nov 14, 2014 at 7:22 PM, wrote: >> > "pg_ctl stop" does't work propley, if --slot option is specified when WAL >> > is flushed only it has switched. >> > These processes still con

Re: [HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-14 Thread Andres Freund
On 2014-11-15 03:25:16 +0900, Fujii Masao wrote: > On Fri, Nov 14, 2014 at 7:22 PM, wrote: > > Hi, > > > > "pg_ctl stop" does't work propley, if --slot option is specified when WAL > > is flushed only it has switched. > > These processes still continue even after the posmaster > > failed:pg_rec

Re: [HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-14 Thread Fujii Masao
On Fri, Nov 14, 2014 at 7:22 PM, wrote: > Hi, > > "pg_ctl stop" does't work propley, if --slot option is specified when WAL is > flushed only it has switched. > These processes still continue even after the posmaster > failed:pg_receivexlog, walsender and logger. I could reproduce this problem

[HACKERS] PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.

2014-11-14 Thread furuyao
Hi, "pg_ctl stop" does't work propley, if --slot option is specified when WAL is flushed only it has switched. These processes still continue even after the posmaster failed:pg_receivexlog, walsender and logger. How to reproduce: 1.Start PostgreSQL 2.Create slot 3.Specify --slot option to pg_re