Re: where should I stick that backup?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: where should I stick that backup?
Date: 2020-04-12 19:24:24
Message-ID: 20200412192424.dh2jyxsagn7xeemg@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2020-04-12 11:04:46 -0400, Robert Haas wrote:
> I would expect that we would want to provide a flexible way for a
> target or filter to be passed options from the pg_basebackup command
> line. So one might for example write this:
>
> pg_basebackup --filter='lz4 -9' --filter='encrypt-with-rot13
> rotations=2' --target='shell ssh rhaas(at)depository pgfile
> create-exclusive - %f.lz4'

My gut feeling is that this would end up with too complicated
pg_basebackup invocations, resulting in the complexity getting
reimplemented in the target command. A lot of users don't want to
figure out what compression, encryption, ... command makes sense for
which archiving target. And e.g. an s3 target might want to integrate
with an AWS HSM etc, making it unattractive to do the encryption outside
the target.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-04-12 19:32:51 Re: pg_validatebackup -> pg_verifybackup?
Previous Message Robert Haas 2020-04-12 19:22:11 Re: cleaning perl code