Re: Disable Streaming Replication without restarting either master or slave - Mailing list pgsql-general

From Fujii Masao
Subject Re: Disable Streaming Replication without restarting either master or slave
Date
Msg-id CAHGQGwFAJF7J+nYt3ujVY64DeJ9RmwPcLDKdPeLksRTNVQCETg@mail.gmail.com
Whole thread Raw
In response to Re: Disable Streaming Replication without restarting either master or slave  (Raghavendra <raghavendra.rao@enterprisedb.com>)
List pgsql-general
On Wed, May 30, 2012 at 3:04 AM, Raghavendra
<raghavendra.rao@enterprisedb.com> wrote:
>> > Since stopping or restarting the postgres servers would involve complete
>> > invalidation of the connection pool [Java/JEE app server pool] that may
>> > take
>> > a few minutes before the application becomes usable, it would be great
>> > if
>> > there is a way we can disable replication [for maintenance reasons like
>> > applying patches or upgrades, etc].
>>
>
> I think even applying patches or upgrades needs restart.

Yep.

>> 3. send SIGTERM signal to currently-running walsender process, e.g., by
>>    "select pg_terminate_backend(pid) from pg_stat_replication".
>
>
> Will it be helpful here sending SIGINT instead of killing ?

No, walsender ignores SIGINT signal.

Regards,

--
Fujii Masao

pgsql-general by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Disable Streaming Replication without restarting either master or slave
Next
From: Mark Phillips
Date:
Subject: full text searching