I wrote:
> If it's just a quick kill, then there's a totally separate bug here for
> Windows. What is likely to happen with the current coding is that a
> failing child thread will queue its error message into the communication
> pipe, and then exit(1), thereby killing the whole pg_dump process before
> the master thread can receive and print the error.
Ah, scratch that --- I hadn't noticed the badly-underdocumented #ifdef
in exit_nicely().
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
