Re: Suppressing duplicate key error messages in

From: Larry Lennhoff <llennhoff(at)pexicom(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Suppressing duplicate key error messages in
Date: 2004-10-17 11:22:16
Message-ID: 6.0.2.0.0.20041017071206.01e9f870@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

At 11:59 PM 10/16/2004, Tom Lane wrote:
>Larry Lennhoff <llennhoff-postgres(at)pexicom(dot)com> writes:
> > Is there any way to suppress this message so that it won't appear in the
> > log? I looked at the documentation and log_min_error_statement looked
> > promising. I set it to panic, but the messages continue. What am I doing
> > wrong?
>
>Did you remember to SIGHUP the postmaster after editing postgresql.conf?

After the crash (caused by the log filling all available disk space) and
restart I tried the following:
pexicast_datran_sg=# show log_min_error_statement;
log_min_error_statement
-------------------------
panic
(1 row)

I did not change the value after the restart. I'm using pexicast
7.3.4. There are two databases in this instance, both have
log_min_error_statement set to panic. Let me know if there is anything
else I can tell you that might help.

Larry

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Christian Fowler 2004-10-17 18:47:46 set AUTOCOMMIT OFF in psqlrc not having affect
Previous Message Tom Lane 2004-10-17 03:59:33 Re: Suppressing duplicate key error messages in postgres log?