Re: where should I stick that backup? - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: where should I stick that backup?
Date
Msg-id CAA4eK1+n5VYoz0Uk0S29EmNXhpHpn_3_cDDY+uWW9syju5RGJQ@mail.gmail.com
Whole thread Raw
In response to Re: where should I stick that backup?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Thu, Apr 16, 2020 at 3:44 AM Andres Freund <andres@anarazel.de> wrote:
>
> > I think having a simple framework in pg_basebackup for plugging in new
> > algorithms would make it noticeably simpler to add LZ4 or whatever
> > your favorite compression algorithm is. And I think having that
> > framework also be able to use shell commands, so that users don't have
> > to wait a decade or more for new choices to show up, is also a good
> > idea.
>
> As long as here's sensible defaults, and so that the user doesn't have
> to specify paths to binaries for the common cases, I'm OK with that. I'm
> not ok with requiring the user to specify shell fragments for things
> that should be built in.
>
> If we think the appropriate way to implement extensible compression is
> by piping to commandline binaries ([1]),
>

I can see how such a scheme could be useful for backups but how do we
restore such a backup?

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: DETACH PARTITION and FOR EACH ROW triggers on partitioned tables
Next
From: Prabhat Sahu
Date:
Subject: Re: [Proposal] Global temporary tables