From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Pg_dump backup
Date: Wed, 23 Feb 2022 16:00:27 +0100
Message-ID: <ec9f488c-586e-b006-6209-1725c1cb2c69@jakobs.com> (raw)
In-Reply-To: <17994ffb-4dac-99aa-b889-523d2f579c83@gmail.com>
References: <CALfOM6JqCfOCz1RQX9TAftuDVVHqe6Hq5u4MPrku=O6g1TPTAA@mail.gmail.com>
<17994ffb-4dac-99aa-b889-523d2f579c83@gmail.com>
Am 23.02.22 um 15:45 schrieb Ron:
> On 2/23/22 8:14 AM, Daulat wrote:
>> H Team,
>>
>> I need your advice.
>> How can we ensure the pg_dump backup is successful?
>
> Check the return code immediately after pg_dump completes:
> pg_dump ....
> echo $?
>
> If it's 0, then pg_dump exited successfully.
>
> Of course, it's always good to test the dump files by restoring them
> on non-prod systems.
>
Correct. On top of this you can also look for these lines at the bottom
of the dump
--
-- PostgreSQL database dump complete
--
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Attachments:
OpenPGP_signature (application/pgp-signature, 202B) download
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: holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: Pg_dump backup
In-Reply-To: <ec9f488c-586e-b006-6209-1725c1cb2c69@jakobs.com>
* 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