Re: guc patch: Make variables fall back to default values

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: Joachim Wieland <joe(at)mcknight(dot)de>
Subject: Re: guc patch: Make variables fall back to default values
Date: 2007-03-10 20:35:38
Message-ID: 200703102135.38560.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Joachim Wieland wrote:
> Attached is the long-awaited guc patch that makes values fall back to
> their default values when they got removed (or commented) from the
> configuration file. This has always been a source of confusion.

This patch makes, in its source code comments and error messages, overly
enthusiastic references to the fact that a parameter setting was
supposedly "commented". The only information that is really available,
however, is that the parameter setting disappeared from the
configuration file, and we should not be making other claims.

Another issue that strikes me is that the GUC code apparently makes
mixed used of palloc and guc_malloc, and this patch continues that.
I'm not sure if this is really well thought out.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2007-03-10 22:10:51 Re: [PATCHES] scan_recycle_buffers
Previous Message Pavel Stehule 2007-03-10 19:29:04 simply custom variables protection