Re: BUG #15271: Documentation / Error reporting on GUC parameter change - Mailing list pgsql-bugs

From Akos Vandra
Subject Re: BUG #15271: Documentation / Error reporting on GUC parameter change
Date
Msg-id CAHHcNofAgZ65zNmKZb-GmnXaSdn3EquacrWpJ+itEiqpeKV=Ow@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15271: Documentation / Error reporting on GUC parameter change  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #15271: Documentation / Error reporting on GUC parameterchange  (Bruce Momjian <bruce@momjian.us>)
List 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@sss.pgh.pa.us> wrote:
Akos Vandra <axos88@gmail.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15271: Documentation / Error reporting on GUC parameter change
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #15271: Documentation / Error reporting on GUC parameterchange