Re: Bug in writeTimeLineHistory

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in writeTimeLineHistory
Date: 2010-10-14 18:17:35
Message-ID: 1287080255.1725.1091.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Agreed, committed and backpatched.

On Thu, 2010-10-14 at 14:11 +0900, Fujii Masao wrote:
> Hi,
>
> --------------
> if (recoveryTarget == RECOVERY_TARGET_XID)
> snprintf(buffer, sizeof(buffer),
> "%s%u\t%s\t%s transaction %u\n",
> (srcfd < 0) ? "" : "\n",
> parentTLI,
> xlogfname,
> recoveryStopAfter ? "after" : "before",
> recoveryStopXid);
> if (recoveryTarget == RECOVERY_TARGET_TIME)
> snprintf(buffer, sizeof(buffer),
> "%s%u\t%s\t%s %s\n",
> (srcfd < 0) ? "" : "\n",
> parentTLI,
> xlogfname,
> recoveryStopAfter ? "after" : "before",
> timestamptz_to_str(recoveryStopTime));
> else
> snprintf(buffer, sizeof(buffer),
> "%s%u\t%s\tno recovery target specified\n",
> (srcfd < 0) ? "" : "\n",
> parentTLI,
> xlogfname);
> --------------
>
> In writeTimeLineHistory, the result of the above first snprintf is always
> overwritten by the following snprintf wrongly. I guess we forgot putting
> "else" in the second "if" statement. I attached the very simple patch.
>
> Since this bug was introduced in v9.0, the patch needs to be backported
> to 9.0.
>
> Regards,
>

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2010-10-14 18:17:58 Re: signal and startup process
Previous Message Dean Rasheed 2010-10-14 18:16:56 Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch