| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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-05 18:48:55 |
| Message-ID: | 1270493335.24910.4701.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
> I was also surprised to note that the Startup process is not signaled by
> WALReceiver when new WAL is received, so it will continue sleeping even
> though it has work to do.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-04-05 19:02:39 | Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per |
| Previous Message | Simon Riggs | 2010-04-05 18:46:37 | Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-04-05 19:02:39 | Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per |
| Previous Message | Simon Riggs | 2010-04-05 18:46:37 | Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per |