| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Chris Travers <chris(dot)travers(at)adjust(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, marco(dot)nenciarini(at)2ndquadrant(dot)it |
| Subject: | Re: WIP: Restricting pg_rewind to data/wal dirs |
| Date: | 2017-10-31 22:24:06 |
| Message-ID: | f731beb1-466c-a5bb-0745-78ee701c8f95@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/30/17 6:36 AM, Michael Paquier wrote:
> On Mon, Oct 30, 2017 at 10:15 AM, Chris Travers
>>
>> How does rep mgr or other programs using pg_rewind know what to exclude?
>
> Good question. Answers could come from folks such as David Steele
> (pgBackRest) or Marco (barman) whom I am attaching in CC.
pgBackRest does not use pg_rewind. However, pgBackRest does use the
same exclusion list for backups as pg_basebackup.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-10-31 22:29:40 | Re: Parallel tuplesort (for parallel B-Tree index creation) |
| Previous Message | Tomas Vondra | 2017-10-31 22:17:05 | Re: PATCH: enabling parallel execution for cursors explicitly (experimental) |