How to turn off DEBUG statements from psql commends

----- Original Message -----

From: peterlen <peteralen@earthlink.net>
To: pgsql-general@postgresql.org
Cc:
Sent: Monday, 10 February 2014, 15:43
Subject: [GENERAL] How to turn off DEBUG statements from psql commends

We are using PostgreSQL 9.3.  Something seems to have changed with our psql
command-line output since we first installed it.  When I run commands at my
plsql prompt, I am getting a lot of debug statements which I was not getting
before.  I am just trying to find out how to tell psql not to display this
output.  As an example, if I were to create a new 'test' schema, the
output
looks like:

gis_demo=# create schema test;
DEBUG:  StartTransactionCommand
DEBUG:  StartTransaction
DEBUG:  name: unnamed; blockState:      DEFAULT; state: INPROGR,

I'm guessing you've got client_min_messages set to one of the debug levels, try setting it to "log" or lower.  What does "SHOW client_min_messages;" say?

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Somehow your postgres log statements are getting echoed to the front
end. Did you change anything about the postgres (server) configuration file?

On Mon, Feb 10, 2014 at 07:43:33AM -0800, peterlen wrote:

We are using PostgreSQL 9.3. Something seems to have changed with our psql
command-line output since we first installed it. When I run commands at my
plsql prompt, I am getting a lot of debug statements which I was not getting
before. I am just trying to find out how to tell psql not to display this
output. As an example, if I were to create a new 'test' schema, the output
looks like:

gis_demo=# create schema test;
DEBUG: StartTransactionCommand
DEBUG: StartTransaction
DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR,
xid/subid/cid:
0/1/0, nestlvl: 1, children:
LOG: statement: create schema test;
DEBUG: ProcessUtility
DEBUG: CommitTransactionCommand
DEBUG: CommitTransaction
DEBUG: name: unnamed; blockState: STARTED; state: INPROGR,
xid/subid/cid:
15099/1/1, nestlvl: 1, children:
CREATE SCHEMA
gis_demo=#

Before, all I would get is the CREATE SCHEMA feedback. Not sure what may
have caused this change on our end but does anyone know how to turn it off?

Thanks - Peter

--
View this message in context: http://postgresql.1045698.n5.nabble.com/How-to-turn-off-DEBUG-statements-from-psql-commends-tp5791250.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

--
Andrew Sullivan
ajs@anvilwalrusden.com

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

2014-02-11 0:43 GMT+09:00 peterlen <peteralen@earthlink.net>:

We are using PostgreSQL 9.3. Something seems to have changed with our psql
command-line output since we first installed it. When I run commands at my
plsql prompt, I am getting a lot of debug statements which I was not getting
before. I am just trying to find out how to tell psql not to display this
output. As an example, if I were to create a new 'test' schema, the output
looks like:

gis_demo=# create schema test;
DEBUG: StartTransactionCommand
DEBUG: StartTransaction
DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR,
xid/subid/cid:
0/1/0, nestlvl: 1, children:
LOG: statement: create schema test;
DEBUG: ProcessUtility
DEBUG: CommitTransactionCommand
DEBUG: CommitTransaction
DEBUG: name: unnamed; blockState: STARTED; state: INPROGR,
xid/subid/cid:
15099/1/1, nestlvl: 1, children:
CREATE SCHEMA
gis_demo=#

Before, all I would get is the CREATE SCHEMA feedback. Not sure what may
have caused this change on our end but does anyone know how to turn it off?

What does "SHOW client_min_messages" return?

This has possibly been set to something other than the default in your
.psqlrc file
or the postgresql.conf file.

Regards

Ian Barwick

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Il 10/02/2014 16:43, peterlen ha scritto:

We are using PostgreSQL 9.3. Something seems to have changed with
our psql command-line output since we first installed it. When I
run commands at my plsql prompt, I am getting a lot of debug
statements which I was not getting before. I am just trying to
find out how to tell psql not to display this output. As an
example, if I were to create a new 'test' schema, the output looks
like:

gis_demo=# create schema test; DEBUG: StartTransactionCommand
DEBUG: StartTransaction DEBUG: name: unnamed; blockState:
DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1,
children: LOG: statement: create schema test; DEBUG:
ProcessUtility DEBUG: CommitTransactionCommand DEBUG:
CommitTransaction DEBUG: name: unnamed; blockState: STARTED;
state: INPROGR, xid/subid/cid: 15099/1/1, nestlvl: 1, children:
CREATE SCHEMA gis_demo=#

You have set the "client_min_messages" to "debug" level. If you launch

SET client_min_messages TO notice;

You should obtain just the "CREATE SCHEMA" message.

Giuseppe.
- --
Giuseppe Broccolo - 2ndQuadrant Italy
PostgreSQL Training, Services and Support
giuseppe.broccolo@2ndQuadrant.it | www.2ndQuadrant.it
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJS+Pj3AAoJELtGpyN/y3je5zMQALBNbdLyIOIUI1cN0nwHX/Wb
vg0QdQ4IOqcZkojEFVspD1dJ6cl827eymmhPgkYwol0VU+Lf7TidQuBrw1Xz1+zq
cMA56atTdl1lHkR+gL9fNSX9xb2h/cTfc5ASm1FbspaiitB3Rx3MqWhJTRKWxwAt
lrVQBt5/OXWr+9UVM0cJkLWhGo5WTtkkLJ2UZy0C5IdldoWy0FN/pxtqx36+iUhH
6/joGV1i4wg9MFBO5CC8+vEiSUirbAjRgKaOfg6a2+htQfQUV7MmA+tZx7Hi2O2n
9jVKkYXHsdLD275lGfI4c3qgBWI9kbXOgJMQUsunXZAZNxXmcoMxFvzYbjaI8zZS
sSCFPt3Ztld9zT81wQMzPYxT8cGEcEfyG97iJQv4Xt7ILcxuxTn2AmmVAQs+JWXK
ISfz68bYlzc3FDO72i7sVhlm1kOXhvSMry3pQuqu/v6E+TJN5OUAX1gGSuG4Cn2O
rGh3THBC/W/8+GjfW51X/FfPPQHjcYqzjs8h3Qn86XiarQYQEMpNhtTdFGdnI1U4
P0dF9fu6k9Yx5MQhp9r/zV9lPLfk8E/cmAyV0xDAuP9Hv1mATmWomFmeIpEx91BM
Afimb8JbOAfmZty/5Yj29WVNeKxa8hkyPplV9qdReup2UfcLddPhxRglZN33Ou8N
GIx7YPPx5xs+mukF1kmg
=QLyE
-----END PGP SIGNATURE-----

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Thanks for all the replies. They were all right on. For some unknown
reason, the client_min_messages was set to DEBUG5. Not sure how this
happened but with your help, I now know how to get it back to where it was.
Thanks again for all the quick feedback.

- Peter

--
View this message in context: http://postgresql.1045698.n5.nabble.com/How-to-turn-off-DEBUG-statements-from-psql-commends-tp5791250p5791274.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general