Re: exit_horribly vs exit_nicely in pg_dump

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Pavel Golub <pavel(at)gf(dot)microolap(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: exit_horribly vs exit_nicely in pg_dump
Date: 2013-11-06 13:47:43
Message-ID: 527A487F.2010205@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Albe Laurenz 2013-11-06 13:59:18 FDW: possible resjunk columns in AddForeignUpdateTargets
Previous Message Peter Eisentraut 2013-11-06 13:39:26 Re: git diff --check whitespace checks, gitattributes