From: | Akos Vandra <axos88(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | bruce(at)momjian(dot)us, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15271: Documentation / Error reporting on GUC parameter change |
Date: | 2018-08-07 21:11:16 |
Message-ID: | CAHHcNofAgZ65zNmKZb-GmnXaSdn3EquacrWpJ+itEiqpeKV=Ow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Yeah I guessed as much :(
It's definitely something worth mentioning in the docs with a fat warning
sign though.
Thanks for looking into it.
Akos
On Tue, Aug 7, 2018, 22:53 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Akos Vandra <axos88(at)gmail(dot)com> writes:
> > But the problem persists even as the database owner, I can't ALTER
> DATABASE
> > (as the db owner) before the extension is loaded into the session.
> > Actually that was the original issue. Non-owners or non-superusers can't
> > use ALTER DATABASE, and that's fine, but not even the DB OWNER can use
> > ALTER DB before a SELECT set_limit(); in case of pg_trgm.
>
> Yeah. It's a design limitation with no easy fix. You just have to
> load the extension so that the code knows the properties of the variable.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2018-08-07 21:43:06 | Re: BUG #15271: Documentation / Error reporting on GUC parameter change |
Previous Message | Tom Lane | 2018-08-07 20:53:56 | Re: BUG #15271: Documentation / Error reporting on GUC parameter change |