Re: [COMMITTERS] pgsql: Upgrade to Autoconf 2.69

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Upgrade to Autoconf 2.69
Date: 2014-01-07 13:19:49
Message-ID: 95257337-421E-474B-9799-3B807974DDD6@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

That was probably me. I'll look into it.

> On Jan 6, 2014, at 11:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> On Sun, Dec 29, 2013 at 02:48:21AM -0500, Tom Lane wrote:
>>> 3. pg_upgrade ignores the fact that pg_resetxlog failed, and keeps going.
>
>> Does pg_resetxlog return a non-zero exit status? If so, pg_upgrade
>> should have caught that and exited.
>
> It certainly does:
>
> if (errno)
> {
> fprintf(stderr, _("%s: could not read from directory \"%s\": %s\n"),
> progname, XLOGDIR, strerror(errno));
> exit(1);
> }
>
> The bug is that pg_upgrade appears to assume (in many places not just this
> one) that exec_prog() will abort if the called program fails, but *it
> doesn't*, contrary to the claim in its own header comment. This is
> because pg_log(FATAL, ...) doesn't call exit(). pg_fatal() does, but
> that's not what's being called in the throw_error case.
>
> I imagine that this used to work correctly and got broken by some
> ill-advised refactoring, but whatever the origin, it's 100% broken today.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2014-01-07 16:28:54 pgsql: Avoid including tablespaces inside PGDATA twice in base backups
Previous Message Tom Lane 2014-01-07 04:40:53 Re: [COMMITTERS] pgsql: Upgrade to Autoconf 2.69

Browse pgsql-hackers by date

  From Date Subject
Next Message MauMau 2014-01-07 13:56:28 Re: [bug fix] multibyte messages are displayed incorrectly on the client
Previous Message Florian Pflug 2014-01-07 12:52:51 Re: ERROR: missing chunk number 0 for toast value