Re: Parallel pg_dump's error reporting doesn't work worth squat

On 12/23/2015 10:16 AM, Tom Lane wrote:

> Depending on timing, this scheme might accidentally fail to fail, but it
> seems fragile as can be.  I would bet that it's prone to deadlocks, quite
> aside from the SIGPIPE problem.  Considering how amazingly ugly the
> underlying code is (exit_horribly is in parallel.c now? Really?), I want
> to rip it out entirely, not try to band-aid it by suppressing SIGPIPE ---
> though likely we need to do that too.
>
> Thoughts?

This is something that should work, period. It should be a showcase for 
the code we ship because it shows how serious we take data integrity 
(backups/restore etc...).

+1 for turning it into something irrefutably as close to perfect as 
humans can produce.

Sincerely,

JD


-- 
Command Prompt, Inc. - http://www.commandprompt.com/  503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.