From: | Anony Mous <A(dot)Mous(at)shaw(dot)ca> |
---|---|
To: | 'Shelby Cain' <alyandon(at)yahoo(dot)com>, 'Dustin Sallings' <dustin(at)spy(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump "what if?" |
Date: | 2004-03-26 14:28:11 |
Message-ID: | 002001c4133e$9150d3b0$7402a8c0@PETER |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks again. I've got it working using the API calls described.
pg_dump does return an exit code of 0 upon success. Does anyone know off
hand what is returned when the process fails?
-Pete
-----Original Message-----
From: Shelby Cain [mailto:alyandon(at)yahoo(dot)com]
Sent: March 24, 2004 4:30 PM
To: Anony Mous; 'Dustin Sallings'
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] pg_dump "what if?"
You could spawn pg_dump via CreateProcess and call
WaitForSingleObject() on the handle that CreateProcess
returns in a worker thread. When the Wait() function
returns, you can then call GetExitCodeProcess() on the
same handle to get the process exit code.
Just a thought.
Regards,
Shelby Cain
--- Anony Mous <A(dot)Mous(at)shaw(dot)ca> wrote:
> 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.
>
>
__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Hatcher | 2004-03-26 14:28:31 | Where are these tables?? |
Previous Message | Jan Wieck | 2004-03-26 13:51:12 | Re: 7.4.2 on Solaris 9 - Error |