From: Rui DeSousa <rui@crazybean.net>
To: Dean Gibson (DB Administrator) <postgresql@mailpen.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: The trap when using pg_dumpall
Date: Sun, 4 Jul 2021 17:32:46 -0400
Message-ID: <46651FE6-5D07-44CF-B7D2-3D807EED198F@crazybean.net> (raw)
In-Reply-To: <13043c13-e8ec-bc93-7a50-0da4a15b1431@mailpen.com>
References: <24285551-fa0c-0b38-5380-a58aca27a8a9@mailpen.com>
<eb726473-ca94-472e-134d-616339bf7576@mailpen.com>
<c0ad847f-7afd-da62-3a4d-453ba4345d7b@sqlexec.com>
<13043c13-e8ec-bc93-7a50-0da4a15b1431@mailpen.com>
> On Jul 4, 2021, at 2:04 AM, Dean Gibson (DB Administrator) <postgresql@mailpen.com> wrote:
>
> Well, I never store the
Well, as long as we’re stating I never’s — let me state mine; I never consider a logical backup (pg_dump) a proper backup. They have their use cases and are a very useful tool; however, I would considered a production database without a physical backup as not being backed up. Logical backups don’t allow for PITR recovery and are very slow in comparison. I only use logical backups for migrations, etc. - more as a tool rather than a backup strategy.
A good practice would be to have a separate instance that can instantiate a point in time recovery. This would allow for the reviewing/exporting required data needed to resolve a given issue.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rui@crazybean.net, postgresql@mailpen.com
Subject: Re: The trap when using pg_dumpall
In-Reply-To: <46651FE6-5D07-44CF-B7D2-3D807EED198F@crazybean.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox