Here's an updated WIP version of the LDC patch. I just spreads the
writes, that achieves the goal of smoothing the checkpoint I/O spikes. I
think sorting the writes etc. is interesting but falls in the category
of further development and should be pushed to 8.4.
The documentation changes are
Zdenek Kotala wrote:
I think this patch has no (or small) impact on functionality and it
should be committed to 8.3
That's really not the test we apply. We are in feature freeze, which
means the only things not on the queue that should get in are bug fixes.
If we don't stick to
Zdenek Kotala [EMAIL PROTECTED] writes:
I think this patch has no (or small) impact on functionality and it
should be committed to 8.3
This missed the feature freeze deadline by well over two months.
It is not a candidate for 8.3.
regards, tom lane
Heikki Linnakangas wrote:
- The signaling between RequestCheckpoint and bgwriter is a bit tricky.
Bgwriter now needs to deal immediate checkpoint requests, like those
coming from explicit CHECKPOINT or CREATE DATABASE commands, differently
from those triggered by checkpoint_segments. I'm
Michael Paesold wrote:
Heikki Linnakangas wrote:
Here's an updated WIP version of the LDC patch. I just spreads the
writes, that achieves the goal of smoothing the checkpoint I/O spikes.
I think sorting the writes etc. is interesting but falls in the
category of further development and should
Alvaro Herrera wrote:
Heikki Linnakangas wrote:
- The signaling between RequestCheckpoint and bgwriter is a bit tricky.
Bgwriter now needs to deal immediate checkpoint requests, like those
coming from explicit CHECKPOINT or CREATE DATABASE commands, differently
from those triggered by
Heikki Linnakangas wrote:
Alvaro Herrera wrote:
if (BgWriterShmem-ckpt_time_warn elapsed_secs
CheckPointWarning)
ereport(LOG,
(errmsg(checkpoints are occurring too
frequently (%d seconds apart),
On 5/27/07, Jim C. Nasby [EMAIL PROTECTED] wrote:
On Mon, May 21, 2007 at 10:48:59AM +0100, Heikki Linnakangas wrote:
IOW it's working as designed. But maybe it's not the desired behavior.
Should we have a special case and always respect the fillfactor when
inserting to the last page of the
