| From: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
|---|---|
| To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
| Cc: | 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:04:54 |
| Message-ID: | CA+h6Ahh5pTnJeeZ5bd063+V84tWdRWWZaMuwm7g9JMLRdbxX6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> > 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.
> 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 ?
---
Regards,
Raghavendra
EnterpriseDB Corporation
Blog: http://raghavt.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2012-05-29 18:37:51 | Re: Disable Streaming Replication without restarting either master or slave |
| Previous Message | Chris Angelico | 2012-05-29 17:56:51 | Re: Interval Division Workaround Suggestions (sub-day intervals only)? |