| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
| Date: | 2009-06-26 09:28:45 |
| Message-ID: | 3f0b79eb0906260228t12cb43e7x6b0ab40d9f97a29a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On Fri, Jun 26, 2009 at 3:22 PM, Heikki
Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Are you actually seeing performance degradation caused by frequent
> pg_control updates? In the simple test scenarios I've tested, pg_control
> is updated only once every few WAL segments, and this with
> shared_buffer=32MB. With larger shared_buffers, it happens even less
> frequently.
Oh, I misunderstood about how UpdateMinRecoveryPoint() is called.
ISTM that recovery is still fast unless shared_buffers is set to unreasonable
value. Sorry for the noise.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-06-26 10:57:39 | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
| Previous Message | Heikki Linnakangas | 2009-06-26 06:36:58 | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |