| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | RSR999GMAILCOM <rsr999(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Using old master as new replica after clean switchover |
| Date: | 2019-02-20 00:44:04 |
| Message-ID: | 20190220004404.GZ15532@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 19, 2019 at 04:27:02PM -0800, RSR999GMAILCOM wrote:
> So wanted to clarify if this procedure really requires the WAL archive
> location on a shared storage ?
Shared storage for WAL archives is not a requirement. It is perfectly
possible to use streaming replication to get correct WAL changes.
Using an archive is recommended for some deployments and depending on
your requirements and data retention policy, still you could have
those archives on a different host and have the restore_command of the
standbyt in recovery or the archive_command of the primary save the
segments to it. Depending on the frequency new WAL segments are
generated, this depends of course.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-02-20 00:48:16 | Re: CPU costs of random_zipfian in pgbench |
| Previous Message | Michael Paquier | 2019-02-20 00:39:01 | Re: Prepared transaction releasing locks before deregistering its GID |