Re: timeline garbage in pg_basebackup (was gcc 4.6 warnings -Wunused-but-set-variable)

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: timeline garbage in pg_basebackup (was gcc 4.6 warnings -Wunused-but-set-variable)
Date: 2011-04-27 17:17:50
Message-ID: BANLkTi=Z49GhgU7BDjw+wT2ik2UFhrDoQQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 27, 2011 at 18:55, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On tis, 2011-03-29 at 23:48 +0300, Peter Eisentraut wrote:
>> The line I marked in pg_basebackup.c might be an actual problem: It
>> goes through a whole lot to figure out the timeline and then doesn't
>> do anything with it.
>
> This hasn't been addressed yet.  It doesn't manifest itself as an actual
> problem, but it looks as though someone had intended something in that
> code and the code doesn't do that.

Do you have a ref to the actual problem? The subject change killed my
threading, the email was trimmed to not include the actual problem,
and it appears not to be listed on the open items list... ;)

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-04-27 17:26:52 Re: SSI non-serializable UPDATE performance
Previous Message Peter Eisentraut 2011-04-27 16:57:05 Re: gcc 4.6 warnings -Wunused-but-set-variable