| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Arthur Silva <arthurprs(at)gmail(dot)com> |
| 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:42:29 |
| Message-ID: | 20141003184229.GJ14522@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 3, 2014 at 03:30:35PM -0300, Arthur Silva wrote:
> > 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
>
> 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.
Well, checkpoint_segments was a similar case where we couldn't give good
tuning advice so we went with a server log file warning if it needed to
be increased --- this might be a similar case.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-10-03 18:49:14 | Re: Fixed xloginsert_locks for 9.4 |
| Previous Message | Tom Lane | 2014-10-03 18:42:24 | Re: Fixed xloginsert_locks for 9.4 |