Re: BUG #15271: Documentation / Error reporting on GUC parameter change

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Akos Vandra <axos88(at)gmail(dot)com>
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 20:53:56
Message-ID: 6376.1533675236@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Akos Vandra 2018-08-07 21:11:16 Re: BUG #15271: Documentation / Error reporting on GUC parameter change
Previous Message Akos Vandra 2018-08-07 20:50:53 Re: BUG #15271: Documentation / Error reporting on GUC parameter change