| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
| Date: | 2009-06-25 16:22:47 |
| Message-ID: | 1245946967.4038.160.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 2009-06-25 at 18:57 +0300, Heikki Linnakangas wrote:
> I came up with the attached patch, which includes Simon's patch to
> have all fsync requests forwarded to bgwriter during archive recovery.
> To fix the startup checkpoint issue, startup process requests a forced
> restartpoint, which will flush any fsync requests bgwriter has
> accumulated, before doing the actual checkpoint in the startup
> process.
That looks fine.
> This is completely untested still, but does anyone immediately see any
> more problems?
Nothing seen.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-06-25 16:27:51 | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
| Previous Message | Heikki Linnakangas | 2009-06-25 16:20:00 | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |