Re: WAL Archiving and base backup

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: WAL Archiving and base backup
Date: 2022-01-15 22:41:55
Message-ID: eb1dddbb-176c-4bac-9b11-512c9b4efbf7@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/14/22 3:42 PM, Adrian Klaver wrote:
> On 1/14/22 13:04, Daniel Westermann (DWE) 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.
>>
>> While I know the reasons for not having something like pgbackrest in
>> core, I think this is a major drawback for the project. People coming
>> from commercial systems are used to have that tooling included by default.
>
> They are also used to paying a big whopping bill, which is why they go
> looking for alternatives. So like most things is it a tradeoff, sweat
> equity vs hard cash.

David Johnston's comment about the docs saying "use pgbackrest or barman,
etc" is a good compromise.

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mladen Gogala 2022-01-16 00:15:18 Re: Assistance with an out of shared memory error
Previous Message Дмитрий Иванов 2022-01-15 09:01:52 Re: [Extern] Re: postgres event trigger workaround