From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: alter user set local_preload_libraries. |
Date: | 2014-07-02 18:48:53 |
Message-ID: | CAHGQGwERUZtZ8wz6S6tY8ongyCLAgiaYJk8CtdxJyUBQV7s22A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 2, 2014 at 11:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> writes:
>> postgres=# alter user horiguti2 set local_preload_libraries='libname';
>> ERROR: parameter "local_preload_libraries" cannot be set after connection start
>
> Hm ... it's kind of annoying that that doesn't work; it's certainly not
> hard to imagine use-cases for per-user or per-database settings of
> local_preload_libraries. However, I'm not sure if we apply per-user or
> per-database settings early enough in backend startup that they could
> affect library loading. If we do, then the ALTER code needs to be
> taught to allow this.
ISTM that's what session_preload_libraries does. Anyway I agree with
Horiguchi that we should remove incorrect description from the document
of old versions.
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-07-02 18:53:37 | Re: alter user set local_preload_libraries. |
Previous Message | Tom Lane | 2014-07-02 18:47:04 | Re: Aggregate function API versus grouping sets |