Re: Bug in parse_basebackup_options Re: [COMMITTERS] pgsql: Make walsender options order-independent

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in parse_basebackup_options Re: [COMMITTERS] pgsql: Make walsender options order-independent
Date: 2011-01-25 09:51:01
Message-ID: AANLkTim=kJTgyCNSCQ3AwHWU5NthvOrGK+qkgC+x3FC3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 25, 2011 at 10:32, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Mon, Jan 24, 2011 at 7:41 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Make walsender options order-independent
>>
>> While doing this, also move base backup options into
>> a struct instead of increasing the number of parameters
>> to multiple functions for each new option.
>
> When I read the include-WAL-in-backup patch, I found that this
> commit had the bug; parse_basebackup_options fails in parsing
> options because of wrong usage of MemSet. Here is the patch.

Wow. I know I fixed that at one point, it must've gone bad again in a
merge. Interestingly enough it works in my environment, but that must
be pure luck.

So thanks - applied.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2011-01-25 09:56:19 Re: Include WAL in base backup
Previous Message Fujii Masao 2011-01-25 09:32:11 Bug in parse_basebackup_options Re: [COMMITTERS] pgsql: Make walsender options order-independent