On Sun, Dec 19, 2010 at 1:35 PM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> Just to point out one concrete problem: the postmaster reads
>> postgresql.conf too, so it would have to do this as well in order to
>> parse postgresql.conf correctly.
>
> Well, if I parse you correctly, in my patch, it does. There's another
> GUC array where to store invalid placeholders so that we can revisit
> later. That even allows custom_variable_classes not to be parsed first
> in the list, even if that's not put into use in the patch.
I bet it doesn't. The *postmaster* never connects to a database, so
which copy of pg_extension does it ever read?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
