From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Pg_dump backup
Date: Wed, 23 Feb 2022 08:45:28 -0600
Message-ID: <17994ffb-4dac-99aa-b889-523d2f579c83@gmail.com> (raw)
In-Reply-To: <CALfOM6JqCfOCz1RQX9TAftuDVVHqe6Hq5u4MPrku=O6g1TPTAA@mail.gmail.com>
References: <CALfOM6JqCfOCz1RQX9TAftuDVVHqe6Hq5u4MPrku=O6g1TPTAA@mail.gmail.com>
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.
--
Angular momentum makes the world go 'round.
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: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Pg_dump backup
In-Reply-To: <17994ffb-4dac-99aa-b889-523d2f579c83@gmail.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