Re: A smaller default postgresql.conf

From: Michael Paesold <mpaesold(at)gmx(dot)at>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joshua Drake <jd(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>
Subject: Re: A smaller default postgresql.conf
Date: 2008-08-20 08:18:19
Message-ID: AF42DC61-B9B5-4CD6-8798-45F12205CC1D@gmx.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:

> On Tuesday 19 August 2008 19:12:16 Tom Lane wrote:
>> Well, why not just make a one-eighty and say that the default
>> postgresql.conf is *empty* (except for whatever initdb puts into it)?
>
> Well, my original implementation of GUC had an empty default
> configuration
> file, which was later craptaculated to its current form based on
> seemingly
> popular demand. I am very happy to work back toward the empty
> state, and
> there appears to be growing support for that.

Yeah, +1 from me.

Perhaps we should still add some comments about the parameters changed
most often, including a link to the documentation of GUC parameters.
As a kind of starting point for (new) users.

Best Regards
Michael Paesold

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paesold 2008-08-20 08:24:43 Re: Patch: plan invalidation vs stored procedures
Previous Message Dave Page 2008-08-20 08:05:57 Re: A smaller default postgresql.conf