Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per
Date: 2010-04-06 07:14:22
Message-ID: 4BBADF4E.5030900@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Simon Riggs wrote:
> On Mon, 2010-04-05 at 19:29 +0100, Simon Riggs wrote:
>
>> Looking through the code some more I note that their are two timing
>> related parameters that are hardcoded into XLogPageRead(). At the very
>> least such things should be #defines, though one of them was previously
>> configurable using pg_standby, so I would like to see them both
>> accessible to user tuning.
>
> ...the code says "we want to react quickly when the next WAL record
> arrives" and then sleeps for 100ms.

The comment continues ", so sleep only a bit". That's in comparison to
the 5 s wait when polling the archive.

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-04-06 07:19:23 Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per
Previous Message Fujii Masao 2010-04-06 05:51:59 Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-04-06 07:19:23 Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per
Previous Message Heikki Linnakangas 2010-04-06 07:09:04 Remaining Streaming Replication Open Items