| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-26 16:13:39 |
| Message-ID: | 4A44F3B3.2090405@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane wrote:
> I wrote:
>> Hmm ... this doesn't really feel cleaner to me, although I'm not sure
>> why not.
>
> Oh, I thought of a more concrete point: InRecovery is inherently a
> system-wide state, but XLogInsertAllowed is *not*. While we write
> the EOR checkpoint, we really want only the bgwriter to be authorized
> to write WAL, but the scheme you propose would effectively authorize
> all processes during that window.
I was thinking of doing the same hack we have now, and set
LocalXLogState to "normal processing" in bgwriter, but leave
SharedXLogState still in "recovery".
It's getting late again, and I'm afraid I have to stop for today :-(.
I'll probably check my emails tomorrow, but probably won't be doing much
else until Monday.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-26 16:18:00 | Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
| Previous Message | Tom Lane | 2009-06-26 16:09:31 | Re: BUG #4888: Removed brackets from Check Constraints expressions |