| From: | François Beausoleil <francois(at)teksol(dot)info> |
|---|---|
| To: | Samba <saasira(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Disable Streaming Replication without restarting either master or slave |
| Date: | 2012-05-29 13:17:29 |
| Message-ID: | 3F310B08-0E32-4007-976B-CE08D1526355@teksol.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi!
Le 2012-05-29 à 06:18, Samba a écrit :
> Is it possible stop/disable streaming replication without stopping or restarting either master or slave servers?
>
> 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].
Are per-chance looking for pg_xlog_replay_pause() and pg_xlog_replay_resume() ?
http://www.postgresql.org/docs/current/static/functions-admin.html#FUNCTIONS-RECOVERY-CONTROL-TABLE
Hope that helps!
François Beausoleil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2012-05-29 13:46:00 | Re: How to handle ALTER TABLE DROP CONSTRAINT, ADD CONSTRAINT USING INDEX with foreign keys |
| Previous Message | Thomas Reiss | 2012-05-29 13:08:30 | How to handle ALTER TABLE DROP CONSTRAINT, ADD CONSTRAINT USING INDEX with foreign keys |