Wow, a response from the famous Tom Lane to my lame problem :-) .
> What I'd try is a "ping" to the database server, and not initiate any
> libpq operation unless the server is answering pings. If you get
> a failure due to connectivity loss midway through an operation,
> PQreset is appropriate then --- but don't do it to recover from
> a momentary network outage.
That's interesting. In general, it's hard to ping from a windows
program, unless you want to repeatedly invoke ping.exe. I'm not sure
that I can even retrieve the result of that. That strikes me as fairly
kludgey - acceptable for some utility shellscript, but probably not
for what is supposed to be a responsive program.
Perhaps it would be preferable to call the function after the
operation, but before the application reports success. I'll look into
it.
Regards,
Peter Geoghegan