pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Suppressing  duplicate key error messages in postgres log?
5+ messages / 3 participants
[nested] [flat]

* Suppressing  duplicate key error messages in postgres log?
@ 2004-10-17 01:35 Larry Lennhoff <llennhoff-postgres@pexicom.com>
  2004-10-17 03:59 ` Re: Suppressing duplicate key error messages in postgres log? Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 5+ messages in thread

From: Larry Lennhoff @ 2004-10-17 01:35 UTC (permalink / raw)
  To: pgsql-admin

Hi

I have a postgres table which relies on a unique index to act as a 
semaphore to share a resource among many competing processes on several 
different servers.  This table is hit multiple times per second.  The 
postgres log is being filled by millions of  messages of the sort 
ERROR:  Cannot insert a duplicate key into unique index ...

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?

Thanks in advance for any assistance

Larry 




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Suppressing duplicate key error messages in postgres log?
  2004-10-17 01:35 Suppressing  duplicate key error messages in postgres log? Larry Lennhoff <llennhoff-postgres@pexicom.com>
@ 2004-10-17 03:59 ` Tom Lane <tgl@sss.pgh.pa.us>
  2004-10-17 11:22   ` Re: Suppressing duplicate key error messages in Larry Lennhoff <llennhoff@pexicom.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Tom Lane @ 2004-10-17 03:59 UTC (permalink / raw)
  To: Larry Lennhoff <llennhoff-postgres@pexicom.com>; +Cc: pgsql-admin

Larry Lennhoff <llennhoff-postgres@pexicom.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?

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Suppressing duplicate key error messages in
  2004-10-17 01:35 Suppressing  duplicate key error messages in postgres log? Larry Lennhoff <llennhoff-postgres@pexicom.com>
  2004-10-17 03:59 ` Re: Suppressing duplicate key error messages in postgres log? Tom Lane <tgl@sss.pgh.pa.us>
@ 2004-10-17 11:22   ` Larry Lennhoff <llennhoff@pexicom.com>
  2004-10-17 21:24     ` Re: Suppressing duplicate key error messages in Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 5+ messages in thread

From: Larry Lennhoff @ 2004-10-17 11:22 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin

At 11:59 PM 10/16/2004, Tom Lane wrote:
>Larry Lennhoff <llennhoff-postgres@pexicom.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




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Suppressing duplicate key error messages in
  2004-10-17 01:35 Suppressing  duplicate key error messages in postgres log? Larry Lennhoff <llennhoff-postgres@pexicom.com>
  2004-10-17 03:59 ` Re: Suppressing duplicate key error messages in postgres log? Tom Lane <tgl@sss.pgh.pa.us>
  2004-10-17 11:22   ` Re: Suppressing duplicate key error messages in Larry Lennhoff <llennhoff@pexicom.com>
@ 2004-10-17 21:24     ` Tom Lane <tgl@sss.pgh.pa.us>
  2004-10-18 02:34       ` Re: Suppressing duplicate key error messages in Larry Lennhoff <llennhoff-postgres@pexicom.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Tom Lane @ 2004-10-17 21:24 UTC (permalink / raw)
  To: Larry Lennhoff <llennhoff@pexicom.com>; +Cc: pgsql-admin

Larry Lennhoff <llennhoff@pexicom.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?

[ slightly more awake now ... ] Actually, PANIC is already the default
value of log_min_error_statement.  I think what you want is
log_min_messages.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Suppressing duplicate key error messages in
  2004-10-17 01:35 Suppressing  duplicate key error messages in postgres log? Larry Lennhoff <llennhoff-postgres@pexicom.com>
  2004-10-17 03:59 ` Re: Suppressing duplicate key error messages in postgres log? Tom Lane <tgl@sss.pgh.pa.us>
  2004-10-17 11:22   ` Re: Suppressing duplicate key error messages in Larry Lennhoff <llennhoff@pexicom.com>
  2004-10-17 21:24     ` Re: Suppressing duplicate key error messages in Tom Lane <tgl@sss.pgh.pa.us>
@ 2004-10-18 02:34       ` Larry Lennhoff <llennhoff-postgres@pexicom.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Larry Lennhoff @ 2004-10-18 02:34 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin


At 05:24 PM 10/17/2004, Tom Lane wrote:
>Larry Lennhoff <llennhoff@pexicom.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?
>
>[ slightly more awake now ... ] Actually, PANIC is already the default
>value of log_min_error_statement.  I think what you want is
>log_min_messages.

Hi

In release 7.3 log_min_messages is called server_min_messages. and setting 
that to log and then doing a pg_ctl restart cleared the problem right up.

Thanks for your help

Larry 




^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2004-10-18 02:34 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-10-17 01:35 Suppressing  duplicate key error messages in postgres log? Larry Lennhoff <llennhoff-postgres@pexicom.com>
2004-10-17 03:59 ` Re: Suppressing duplicate key error messages in postgres log? Tom Lane <tgl@sss.pgh.pa.us>
2004-10-17 11:22   ` Re: Suppressing duplicate key error messages in Larry Lennhoff <llennhoff@pexicom.com>
2004-10-17 21:24     ` Re: Suppressing duplicate key error messages in Tom Lane <tgl@sss.pgh.pa.us>
2004-10-18 02:34       ` Re: Suppressing duplicate key error messages in Larry Lennhoff <llennhoff-postgres@pexicom.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox