supressing NOTICE messages on Windows/cygwin only not working?

[Alex Soto]

Hi,

I'm noticing NOTICE messages can't be turned off with my cygwin-based
platform. I've had other's confirm it works on linux.
Here is my session:

$ psql -U postgresql itn
Welcome to psql 7.4.5, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit

postgresql@[local][itn]>SET client_min_mess ages TO error;
SET
postgresql@[local][itn]>SHOW client_min_mess ages;
client_min_mess ages
---------------------
error
(1 row)

postgresql@[local][itn]>CREATE TABLE foobar(
itn(# id INTEGER NOT NULL,
itn(# PRIMARY KEY (id)
itn(# );
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "foobar_pke y" for
table "foobar"
CREATE TABLE
postgresql@[local][itn]>SHOW client_min_mess ages;
client_min_mess ages
---------------------
error
(1 row)

postgresql@[local][itn]>

See anything wrong with what I did? There must be some setting I
haven't done. I'm on windows xp pro using the cygwin standard
install.

TIA

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

[Tom Lane]

Alex Soto <ap****@gmail.c om> writes:

I'm noticing NOTICE messages can't be turned off with my cygwin-based
platform. I've had other's confirm it works on linux.

The SET will definitely turn off messages that the backend thinks it is
delivering to the client. However, it won't turn off logging of those
same messages in the postmaster log --- which may just be standard
error. Allow me to guess a couple things:

1. You originally launched the postmaster from the same terminal window
you are now running psql in, and you didn't do anything to redirect its
error log to a file or /dev/null or syslog or whatever.

2. Before you changed client_min_mess ages you were actually seeing *two*
copies of these messages, one sent through psql and one popping up
because you are reading the postmaster's stderr.

While you could make this go away by changing log_min_message s, a better
idea would be to redirect postmaster stderr someplace when you start it.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Alex Soto]

Thanks Tom,

Embarassingly correct guesses. Thanks for the quick response.
On Tue, 07 Sep 2004 11:29:17 -0400, Tom Lane <tg*@sss.pgh.pa .us> wrote:

Alex Soto <ap****@gmail.c om> writes:

I'm noticing NOTICE messages can't be turned off with my cygwin-based
platform. I've had other's confirm it works on linux.

The SET will definitely turn off messages that the backend thinks it is
delivering to the client. However, it won't turn off logging of those
same messages in the postmaster log --- which may just be standard
error. Allow me to guess a couple things:

1. You originally launched the postmaster from the same terminal window
you are now running psql in, and you didn't do anything to redirect its
error log to a file or /dev/null or syslog or whatever.

2. Before you changed client_min_mess ages you were actually seeing *two*
copies of these messages, one sent through psql and one popping up
because you are reading the postmaster's stderr.

While you could make this go away by changing log_min_message s, a better
idea would be to redirect postmaster stderr someplace when you start it.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster