| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Chris Travers <chris(dot)travers(at)adjust(dot)com> |
| Cc: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_rewind and postgresql.conf |
| Date: | 2018-05-04 12:53:32 |
| Message-ID: | 20180504125332.GA1592@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 04, 2018 at 02:10:46PM +0200, Chris Travers wrote:
> Yes that is copied currently by pg_rewind, as are server logs if they are
> in the data directory.
Yes, that is valid for all the existing versions of pg_rewind in the
core tree, as well as what I maintain for VMware (9.3 and 9.4
versions).
> I think replication slots also might be copied but would have to check.
No. At least not since 266b6ac which will be part of Postgres 11. All
that is described in the documentation (see the bottom):
https://www.postgresql.org/docs/devel/static/app-pgrewind.html
Those are copied up to v10 though.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Moench-Tegeder | 2018-05-04 12:57:16 | Re: pg_rewind and postgresql.conf |
| Previous Message | Alexander Lakhin | 2018-05-04 12:30:56 | Re: make installcheck-world in a clean environment |