Re: pg_dump why no indicator of completion

From: Holger Jakobs <holger(at)jakobs(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org, richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>
Subject: Re: pg_dump why no indicator of completion
Date: 2023-05-01 07:43:35
Message-ID: D2233CA3-EC91-4154-AD06-730E3E574DE5@jakobs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

At least it you use plaintext dump, you can check with tail dumpFile for the message

Am 1. Mai 2023 02:18:06 MESZ schrieb richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>:
>Hi all,
>
>I've been working with pg_dump and one thing that's always struck me as
>strange is that there never seems to be an indication in the log that the
>pg_dump process completed successfully.
>
>For example, I've been running a bunch of backups with pg_dump in directory
>mode with multiple jobs. When I come back several hours later there are no
>pg_dump processes running. The log is filled with:
>
>dumping contents of foo
>finished item 123456 of TABLE DATA bar
>etc.
>
>
>Other than trying to restore the multi terabyte database somewhere else is
>there any way to know that it actually finished successfully?
>
>Why doesn't pg_dump add a line in the output like:
>
>pg_backup finished
>
>when it's completed successfully?
>
>This seems like a terrible oversight.
>
>Am I missing something obvious?
>
>Thanks,
>rik.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Frank Lanitz 2023-05-01 10:12:25 Re: pg_dump why no indicator of completion
Previous Message Laurenz Albe 2023-05-01 04:09:57 Re: how to list privileges on the database object itself via SQL?