| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Vladimir Borodin <root(at)simply(dot)name> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: pg_rewind to skip config files |
| Date: | 2017-09-05 12:48:20 |
| Message-ID: | CAB7nPqRj3V1LJg2fM5OrTQ36SjWYUHZw_UTaVTTKjABheoZW3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 5, 2017 at 9:40 PM, Vladimir Borodin <root(at)simply(dot)name> wrote:
> 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.
Ah, yeah, true. I do use pg_receivexlog --compress for that locally
and do a bulk copy of only the compressed WALs needed, when needed...
So there is a guarantee that completed segments are durable locally,
which is very useful. You should definitely avoid putting that in
PGDATA though, the same counts for tablespaces within PGDATA for
example.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2017-09-05 13:01:54 | Re: PoC plpgsql - possibility to force custom or generic plan |
| Previous Message | Daniel Gustafsson | 2017-09-05 12:43:48 | Re: Making clausesel.c Smarter |