From: | Arthur Silva <arthurprs(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Gregory Smith <gregsmithpgsql(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fixed xloginsert_locks for 9.4 |
Date: | 2014-10-03 18:30:35 |
Message-ID: | CAO_YK0WLTDGRDUryvsdpftrjkMQSvxuESotCg7KkQb1niyUt2w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 3, 2014 at 3:10 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Fri, Oct 3, 2014 at 02:07:45PM -0400, Bruce Momjian wrote:
> > On Fri, Oct 3, 2014 at 03:00:56PM -0300, Arthur Silva wrote:
> > > I remember Informix had a setting that had no description except
> "try
> > > different values to see if it helps performance" --- we don't want
> to do
> > > that.
> > >
> > > What if we emit a server message if the setting is too low?
> That's how
> > > we handle checkpoint_segments.
> > >
> > > Not all GUC need to be straight forward to tune.
> > > If the gains are worthy I don't see any reason not to have it.
> >
> > Every GUC add complexity to the system because people have to understand
> > it to know if they should tune it. No GUC is zero-cost.
>
> Please see my blog post about the cost of adding GUCs:
>
> http://momjian.us/main/blogs/pgblog/2009.html#January_10_2009
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + Everyone has their own god. +
>
That's true Bruce (nice post, it was a good reading).
But how can we ignore 25%+ improvements (from 8 to 24)?
At very least we should delivery some pretty good defaults.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-10-03 18:33:46 | Re: replicating DROP commands across servers |
Previous Message | Heikki Linnakangas | 2014-10-03 18:21:12 | Re: replicating DROP commands across servers |