Re: Why do we still have commit_delay and commit_siblings? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Why do we still have commit_delay and commit_siblings?
Date
Msg-id CA+TgmoYOW8OQugbJT2=0HcoKCgbb+Y0NNAbz0f+n4BvRFX-XZQ@mail.gmail.com
Whole thread Raw
In response to Re: Why do we still have commit_delay and commit_siblings?  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Why do we still have commit_delay and commit_siblings?
List pgsql-hackers
On Mon, May 14, 2012 at 2:07 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Keeping a parameter without any clue as to whether it has benefit is
> just wasting people's time.

No, arguing that we should remove a parameter because it's useless
when you haven't bothered to test whether or not it actually is
useless is wasting people's time.

> We don't ADD parameters based on supposition, why should we avoid
> removing parameters that have no measured benefit?

If they have no actual benefit, of course we should remove them.  If
they have no measured benefit because no one has bothered to measure,
that's not a reason to remove them.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Why do we still have commit_delay and commit_siblings?
Next
From: Heikki Linnakangas
Date:
Subject: Re: Why do we still have commit_delay and commit_siblings?