On Fri, 2007-06-15 at 11:34 +0100, Heikki Linnakangas wrote:
> - What units should we use for the new GUC variables? From
> implementation point of view, it would be simplest if
> checkpoint_write_rate is given as pages/bgwriter_delay, similarly to
> bgwriter_*_maxpages. I never liked those *_m
On Fri, 2007-06-15 at 13:11 +0200, 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 t
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> another question: if the fillfactor is 100% then is a complete waste
> of time to look for a suggested block. maybe we could check for that?
No, it isn't, since the page might have been vacuumed since it was last
filled up.
re
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> checkpoint_maxpages would seem like a better name; we've already had
> those _maxpages settings for 3 releases, so changing that is not really
> an option (at so late a stage).
Sure it is. We've never promised stability of obscure tuning settings.
For s
On Sat, 2007-06-16 at 11:02 -0400, Tom Lane wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
> > checkpoint_maxpages would seem like a better name; we've already had
> > those _maxpages settings for 3 releases, so changing that is not really
> > an option (at so late a stage).
>
> Sure it is.
On 6/16/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> another question: if the fillfactor is 100% then is a complete waste
> of time to look for a suggested block. maybe we could check for that?
No, it isn't, since the page might have been vacuumed since
Forwarding to -patches. FWIW I looked around a little and couldn't find a
suitable replacement, but if someone knows of one (or can find one) we could
replace the link rather than remove it.
On Friday 15 June 2007 20:23, David Gardner wrote:
> I was just reading the pgsql developer faq :
> htt
Completed all of the agreed changes for TG:
- WAL writer now runs always, wal_writer_delay = 50ms (default)
- when transaction_guarantee = off we record the latest LSN
- when we set xact hint bits we look at the latest LSN
- added database-level stats to show guaranteed commits
- fsync parameter s
Jaime Casanova wrote:
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
> insert
