| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_receivexlog or archive_command |
| Date: | 2019-09-23 11:56:47 |
| Message-ID: | e3ebc4bb-247e-bfcf-21e0-96cdcf633376@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 23.09.19 um 13:44 schrieb Luca Ferrari:
> On Mon, Sep 23, 2019 at 10:55 AM Andreas Kretschmer
> <andreas(at)a-kretschmer(dot)de> wrote:
>> you can use both of them, and you should consider "Barman".
> If I remember well Barman uses pg_receivexlog when streaming, and
> archive_command when doing a "normal" backup.
Barman < version 2 can only archive_command, version 2 and higher can both.
> Also pgbackrest is another good tool for backup.
> The idea here should be not reinventing the wheel.
ack.
Regards, Andreas
> --
> 2ndQuadrant - The PostgreSQL Support Company.
> www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2019-09-23 12:23:27 | Re: unable to drop index because it does not exists |
| Previous Message | Luca Ferrari | 2019-09-23 11:44:44 | Re: pg_receivexlog or archive_command |