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 16:27:05 |
Message-ID: | AANLkTikgsczXANu0XoExhaexP=7QjCfpTCVAqCKJedti@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 20, 2010 at 3:56 AM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I bet it doesn't. The *postmaster* never connects to a database, so
>> which copy of pg_extension does it ever read?
>
> None, which does it need to read? My answer is none, you're saying it's
> wrong, I don't get why. postmaster surely has no business with what's in
> a specific database and no use at all of placeholder GUCs, right?
Let's take a concrete example. Suppose the user installs the
extension 'pg_stat_statements' and puts the following into their
postgresql.conf:
pg_stat_statements.max = 31415;
The effect of that has to be that the postmaster adds a certain amount
of space to PostgreSQL's initial shared memory allocation. That means
the postmaster has to know that pg_stat_statements is a valid custom
variable class.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-12-20 16:27:47 | Re: bug in SignalSomeChildren |
Previous Message | Andrew Dunstan | 2010-12-20 16:26:17 | Re: MingW and MiniDumps |