Re: BUG #15271: Documentation / Error reporting on GUC parameterchange

On Tue, Aug  7, 2018 at 11:11:16PM +0200, Akos Vandra wrote:
> Yeah I guessed as much :(
> 
> It's definitely something worth mentioning in the docs with a fat warning sign
> though.

We do have a _vague_ warning sign.  ;-)

---------------------------------------------------------------------------


> 
> 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
> 

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +