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

From Tom Lane
Subject Re: BUG #15271: Documentation / Error reporting on GUC parameter change
Date
Msg-id 6376.1533675236@sss.pgh.pa.us
Whole thread Raw
In response to BUG #15271: Documentation / Error reporting on GUC parameter change  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15271: Documentation / Error reporting on GUC parameter change  (Akos Vandra <axos88@gmail.com>)
List pgsql-bugs
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: Akos Vandra
Date:
Subject: Re: BUG #15271: Documentation / Error reporting on GUC parameter change
Next
From: Akos Vandra
Date:
Subject: Re: BUG #15271: Documentation / Error reporting on GUC parameter change