| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
| Cc: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>, Samba <saasira(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Disable Streaming Replication without restarting either master or slave |
| Date: | 2012-05-29 18:38:58 |
| Message-ID: | CAHGQGwFAJF7J+nYt3ujVY64DeJ9RmwPcLDKdPeLksRTNVQCETg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, May 30, 2012 at 3:04 AM, Raghavendra
<raghavendra(dot)rao(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Phillips | 2012-05-29 21:28:29 | full text searching |
| Previous Message | Fujii Masao | 2012-05-29 18:37:51 | Re: Disable Streaming Replication without restarting either master or slave |