Re: ThisTimeLineID in checkpointer and bgwriter processes

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ThisTimeLineID in checkpointer and bgwriter processes
Date: 2012-12-20 23:37:15
Message-ID: CAHGQGwFk8Lcj+nomVpO_TpADT9vAmAWkbReNc+WrMdne=DC0_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 21, 2012 at 2:45 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> On 20.12.2012 18:19, Fujii Masao wrote:
>>
>> InstallXLogFileSegment() also uses ThisTimeLineID. But your recent commit
>> doesn't take care of it and prevents the standby from recycling the WAL
>> files
>> properly. Specifically, the standby recycles the WAL file to wrong name.
>
>
> A-ha, good catch. So that's actually a live bug in 9.1 and 9.2 as well:
> after the recovery target timeline has changed, restartpoints will continue
> to preallocate/recycle WAL files for the old timeline. That's otherwise
> harmless, but the useless WAL files waste space, and walreceiver will have
> to always create new files.
>
> So instead of always running with ThisTimeLineID = 0 in the checkpointer
> process, I guess we'll have to update it to the timeline being replayed,
> when creating a restartpoint.

Yes. Thanks for fixing that.

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-12-20 23:47:32 Re: Parser Cruft in gram.y
Previous Message McDevitt, Charles 2012-12-20 23:23:07 Re: Parser Cruft in gram.y