Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Tom Lane wrote:
>> The behavior you seem to have in mind would be completely disastrous
>> from a performance standpoint, as we'd be writing and fsyncing
>> pg_control constantly during a recovery.
> Please define "constantly". We discussed that part of the patch here:
Okay, after reading the code a bit more I found this:
* To avoid having to update the control file too often, we update it
* all the way to the last record being replayed, even though 'lsn'
* would suffice for correctness.
which should alleviate the too-many-writes syndrome. Never mind that
complaint then. (But shouldn't there be an Assert that this is >= lsn?)
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2009-06-25 22:40:43|
|Subject: Re: BUG #4879: bgwriter fails to fsync the file in recovery mode |
|Previous:||From: William Chu||Date: 2009-06-25 22:22:59|
|Subject: BUG #4884: Misleading error message|