Re: Fixed xloginsert_locks for 9.4

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 23:10:28
Message-ID: 20141003231028.GN14522@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Oct 4, 2014 at 12:00:36PM +1300, Mark Kirkwood wrote:
> >I don't think we can offer absolutely accurate tuning advice, but I'm
> >sure we can give some guidance. Let me try.
> >
>
> +1
>
> I think it is ok to document our reason for providing the new GUC -
> along with that fact that it is a new one and we need more field
> testing and benchmarks to provide comprehensive advice about how to
> set - and recommend leaving it alone unless consult with
> experts/this list etc.

I predict that such a setting will remain in postgresql.conf for years
with almost zero activity, as have other similar efforts.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-10-03 23:23:37 strip nulls functions for json and jsonb
Previous Message Mark Kirkwood 2014-10-03 23:00:36 Re: Fixed xloginsert_locks for 9.4