From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL-Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Extensions and custom_variable_classes |
Date: | 2010-12-20 04:42:24 |
Message-ID: | AANLkTikxANoyBQoN6=xE7h+aPrKktSm-Yoh+GUETNPH8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Dec 19, 2010 at 1:35 PM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-12-20 05:10:38 | Re: pg_ctl and port number detection |
Previous Message | David Christensen | 2010-12-20 04:00:02 | Re: plperlu problem with utf8 |