Re: Small bug on CREATE EXTENSION pgq...

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Small bug on CREATE EXTENSION pgq...
Date: 2015-01-29 03:28:21
Message-ID: 20150129032821.GI3854@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* David G Johnston (david(dot)g(dot)johnston(at)gmail(dot)com) wrote:
> Jerry Sievers-3 wrote
> > Hackers; I noticed this trying to import a large pg_dump file with
> > warnings supressed.
> >
> > It seems loading pgq sets client_min_messages to warning and leaves it
> > this way which defeats an attempt to change the setting prior and have
> > it stick.
> >
> > I tested with several other extensions in same DB and only pgq has the
> > problem.
> >
> > Sorry if this is known/fixed already.
>
> This is not part of PostgreSQL proper and thus not supported by -hackers;
> you should report this directly to the authors.

Ehh.. Shouldn't we try to take a bit more care that we reset things
after a CREATE EXTENSION is run? Not really sure how much effort we
want to put into it, but I see a bit of blame on both sides here.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Johnston 2015-01-29 03:41:48 Re: Small bug on CREATE EXTENSION pgq...
Previous Message David G Johnston 2015-01-29 03:24:43 Re: Small bug on CREATE EXTENSION pgq...