Postgres Pro
Downloads
Home   >   mailing lists

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

From Bruce Momjian
Subject Re: exit_horribly vs exit_nicely in pg_dump
Date
Msg-id 20140305231549.GC20275@momjian.us
Whole thread Raw
In response to Re: exit_horribly vs exit_nicely in pg_dump  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tree view 
On Wed, Nov  6, 2013 at 08:47:43AM -0500, Peter Eisentraut wrote:
> 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.

Fixed in attached applied patch.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +
Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_ctl status with nonexistent data directory
Next
From: Andres Freund
Date:
Subject: Re: Unportable coding in reorderbuffer.h