Thanks, but I’m calling a win32 compiled version of pg_dump, which runs asynchronously to the rest of my code (sorry I was vague in my first message). As such, I don’t see how I can use the return value. My only other thought was to check for the existence of the file, which would be useless if the file represented an incomplete dump.
-----Original Message-----
From: Dustin Sallings [mailto:dustin@spy.net]
Sent: March 24, 2004 1:26 PM
To: Anony Mous
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_dump "what if?"
On Mar 24, 2004, at 11:42, Anony Mous wrote:
I’m running pg_dump 7.3.4. I have a nightly process that dumps a database via pg_dump, and then checks for the existence of the dumped file afterwards to confirm that the dump actually occurred. Just wondering, however, if a corrupt disk prevented pg_dump from executing fully, would there still be an output file up to the point where the corruption was encountered? If so, does anyone have any suggestions on another method to confirm whether or not the db was successfully dumped?
The exit code?
--
Dustin Sallings
