From: | Chris Travers <chris(dot)travers(at)adjust(dot)com> |
---|---|
To: | Vladimir Borodin <root(at)simply(dot)name> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: pg_rewind to skip config files |
Date: | 2017-09-05 12:42:39 |
Message-ID: | CAN-RpxCL41rt48xqtxDG8+vyXSBgszfsyfrz0vyLH7bW_-Q7VA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 5, 2017 at 2:40 PM, Vladimir Borodin <root(at)simply(dot)name> wrote:
>
> 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.
>
How would this work when it comes to rewinding against a file directory?
>
> --
> May the force be with you…
> https://simply.name
>
>
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2017-09-05 12:43:48 | Re: Making clausesel.c Smarter |
Previous Message | Peter Eisentraut | 2017-09-05 12:42:11 | Re: Disallowing multiple queries per PQexec() |