Re: Proposal to Re-Order Postgresql.Conf, part II - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Proposal to Re-Order Postgresql.Conf, part II
Date
Msg-id 27249.1054913398@sss.pgh.pa.us
Whole thread Raw
In response to Proposal to Re-Order Postgresql.Conf, part II  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Proposal to Re-Order Postgresql.Conf, part II  (Josh Berkus <josh@agliodbs.com>)
Re: Proposal to Re-Order Postgresql.Conf, part II  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> 1) Are any additional changes expected for GUC.c before feature-freeze?

I'm still thinking of adding an am_superuser variable so that psql can
rely on the new ParameterStatus mechanism instead of explicit queries to
find out if you're superuser.  But this would be a read-only variable
and so should not appear in postgresql.conf.  Offhand I'm not aware of
any other proposed additions ... but something might turn up.

> 2) Are all of the new GUC.c variables for 7.4 already documented in the CVS 
> docs?

They should be.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: Wrong version of jdbc in 7.3.3 rpms
Next
From: Bruce Momjian
Date:
Subject: Re: Removing a user's password