From: | Vladimir Borodin <root(at)simply(dot)name> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: pg_rewind to skip config files |
Date: | 2017-09-05 12:40:20 |
Message-ID: | 48DF1E45-E52F-4B4A-A428-9E905FC02644@simply.name |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 5 сент. 2017 г., в 14:04, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> написал(а):
>
>> For example, in archive_command we put WALs for archiving from
>> pg_xlog/pg_wal into another directory inside PGDATA and than another cron
>> task makes real archiving. This directory ideally should be skipped by
>> pg_rewind, but it would not be handled by proposed change.
>
> I would be curious to follow the reasoning for such a two-phase
> archiving (You basically want to push it in two places, no? But why
> not just use pg_receivexlog then?). This is complicated to handle from
> the point of view of availability and backup reliability + durability.
We do compress WALs and send them over network. Doing it via archive_command in single thread is sometimes slower than new WALs are written under heavy load.
--
May the force be with you…
https://simply.name
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2017-09-05 12:41:27 | Re: Proposal: pg_rewind to skip config files |
Previous Message | Chris Travers | 2017-09-05 12:21:54 | Re: Proposal: pg_rewind to skip config files |