Re: WAL Archiving and base backup

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: WAL Archiving and base backup
Date: 2022-01-14 21:00:33
Message-ID: CAKFQuwZX6YXPNtC6pJJzYj2DZGHfiWPmGatxDteomyWNTMkSqg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jan 14, 2022 at 1:48 PM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:

> On 1/14/22 1:40 PM, Stephen Frost wrote:
> [snip]
> > We shouldn't be trying to provide
> > documentation around how to write a tool like pgbackrest, we should,
> > instead, have a tool like pgbackrest in core with its own documentation,
> > as most other RDBMS's do.
>
> That's an excellent solution to this problem.
>
>
I still don't really understand what is so great about it. About its only
redeeming feature is a declaration that "it is in core" and that newcomers
can just default to it without thinking. I'd rather just play favorites
and write "use pgbackrest" in our documentation. Or some hybrid approach
where we don't just pick one but instead guide people to the community
solutions that are out there. I don't think I really want the people
responsible for core to spend time on writing end-user backup tooling.
Their time is much more valuably spent working on the core product.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Westermann (DWE) 2022-01-14 21:04:59 Re: WAL Archiving and base backup
Previous Message Ron 2022-01-14 20:48:50 Re: WAL Archiving and base backup