Re: pg_dump "what if?"

From: Shelby Cain <alyandon(at)yahoo(dot)com>
To: Anony Mous <A(dot)Mous(at)shaw(dot)ca>, 'Dustin Sallings' <dustin(at)spy(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump "what if?"
Date: 2004-03-24 23:29:51
Message-ID: 20040324232951.35274.qmail@web41602.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-03-24 23:50:47 Re: ERROR: column "currec" does not exist while calling function with 'record' (or %rowtype% argument
Previous Message Alan Carbutt 2004-03-24 23:20:13 Adding flexibilty to queries