Postgres Pro
Downloads
Home   >   mailing lists

Re: exit_horribly vs exit_nicely in pg_dump - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: exit_horribly vs exit_nicely in pg_dump
Date
Msg-id 527A487F.2010205@gmx.net
Whole thread Raw
In response to exit_horribly vs exit_nicely in pg_dump  (Pavel Golub <pavel@microolap.com>)
Responses Re: exit_horribly vs exit_nicely in pg_dump  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Tree view 
On 11/5/13, 8:46 AM, Pavel Golub wrote:
> I suppose this should be call to exit_nicely() for all possible cases.
> 
> The only need for calling exit_horribly() is when we are deep down in
> the multithreaded code, AFAIK.

Doesn't hurt either, though.  But it would be OK to make this more
consistent.

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: git diff --check whitespace checks, gitattributes
Next
From: Albe Laurenz
Date:
Subject: FDW: possible resjunk columns in AddForeignUpdateTargets