Re: Streaming Replication: Checkpoint_segment and wal_keep_segments on standby

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "Sander, Ingo (NSN - DE/Munich)" <ingo(dot)sander(at)nsn(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Streaming Replication: Checkpoint_segment and wal_keep_segments on standby
Date: 2010-06-02 11:40:52
Message-ID: 4C064344.7040601@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/06/10 06:23, Fujii Masao wrote:
> On Mon, May 31, 2010 at 7:17 PM, Fujii Masao<masao(dot)fujii(at)gmail(dot)com> wrote:
>> 4) Change it so that checkpoint_segments takes effect in standby mode,
>> but not during recovery otherwise
>
> I revised the patch to achieve 4). This will enable checkpoint_segments
> to trigger a restartpoint like checkpoint_timeout already does, in
> standby mode (i.e., streaming replication or file-based log shipping).

Hmm, XLogCtl->Insert.RedoRecPtr is not updated during recovery, so this
doesn't work.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-06-02 11:56:51 proposal - custom format for date, timestamp
Previous Message Heikki Linnakangas 2010-06-02 11:16:58 Re: [BUGS] BUG #5487: dblink failed with 63 bytes connection names