| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>, Ron <ronljohnsonjr(at)gmail(dot)com>, "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-14 21:42:17 |
| Message-ID: | a36c28a1-d0d5-4846-513b-55448245a2e3@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
>
> +1 for having that in core
>
> Regards
> Daniel
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gautam Bellary | 2022-01-15 02:25:51 | Re: Assistance with an out of shared memory error |
| Previous Message | Daniel Westermann (DWE) | 2022-01-14 21:04:59 | Re: WAL Archiving and base backup |