| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, 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 14:35:44 |
| Message-ID: | 4A438B40.6020107@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas wrote:
> Hmm, what happens when the startup process performs a write, and
> bgwriter is not running? Do the fsync requests queue up in the shmem
> queue until the end of recovery when bgwriter is launched? I guess I'll
> have to try it out...
Oh dear, doesn't look good. The startup process has a pendingOpsTable of
its own. bgwriter won't fsync() files that the startup process has
written itself. That needs to be fixed, or you can lose data when an
archive recovery crashes after a restartpoint.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-25 14:49:09 | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
| Previous Message | Andreas Wenk | 2009-06-25 14:27:21 | BUG #4881: KDE 4.2 not running any more when installing one click installer from Enterprise DB |