Re: Load Distributed Checkpoints, revised patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Load Distributed Checkpoints, revised patch
Date: 2007-06-16 15:02:33
Message-ID: 11092.1182006153@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"Simon Riggs" <simon(at)2ndquadrant(dot)com> 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 something as commonly set from-an-application as, say, work_mem
(nee sort_mem), it's worth worrying about backward compatibility.
But not for things that in practice would only be set from
postgresql.conf. It's never been possible to just copy your old .conf
file without any thought when moving to a new release.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-06-16 16:46:12 Re: Load Distributed Checkpoints, revised patch
Previous Message Tom Lane 2007-06-16 14:56:24 Re: Maintaining cluster order on insert

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2007-06-16 16:46:12 Re: Load Distributed Checkpoints, revised patch
Previous Message Tom Lane 2007-06-16 14:56:24 Re: Maintaining cluster order on insert