Small bug on CREATE EXTENSION pgq...

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.

Thanks


sj$ cat q
select version();

create database foo template template0;
\c foo

show client_min_messages;

create extension pgq;

show client_min_messages;
reset client_min_messages;
show client_min_messages;

create extension pgq_node;

show client_min_messages;

\c postgres

drop database foo;


sj$ /usr/local/postgresql-9.3/bin/psql -ef q  --no-psqlrc
select version();                                          version                                            
----------------------------------------------------------------------------------------------PostgreSQL 9.3.4 on
x86_64-unknown-linux-gnu,compiled by gcc (Debian 4.7.2-5) 4.7.2, 64-bit
 
(1 row)

create database foo template template0;
CREATE DATABASE
psql (9.3.5, server 9.3.4)
You are now connected to database "foo" as user "jsievers".
show client_min_messages;client_min_messages 
---------------------notice
(1 row)

create extension pgq;
CREATE EXTENSION
show client_min_messages;client_min_messages 
---------------------warning
(1 row)

reset client_min_messages;
RESET
show client_min_messages;client_min_messages 
---------------------notice
(1 row)

create extension pgq_node;
CREATE EXTENSION
show client_min_messages;client_min_messages 
---------------------notice
(1 row)

psql (9.3.5, server 9.3.4)
You are now connected to database "postgres" as user "jsievers".
drop database foo;
DROP DATABASE
sj$ 
-- 
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800