Skip site navigation (1) Skip section navigation (2)

Proposed GUC Variable

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Proposed GUC Variable
Date: 2002-08-23 02:04:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches

My primary use of Postgres is as the backend database for a busy web site.
We have a cron job that just emails us the tail of our database, php, apache
logs every night.  That way we can see some problems.

These logs almost always contain some errors.  For instance, this is what I
see at the moment:

2002-08-22 19:21:57 ERROR:  pg_atoi: error in "334 - 18k": can't parse " -

Now there's plenty of places that accept numeric input in the site and
obviously there's a bug in some script somewhere that's not filtering the
input properly or something.  However - the error message above is useless
to me!!!

So, what I'd like to propose is a new GUC variable called
'debug_print_query_on_error' or something.  Instead of turning on
debug_print_query and having my logs totally spammed up with sql, this GUC
variable would only print the query if an actual ERROR occurred.  This way I
could nail the error very quickly by simply finding the query in my

Is this possible?  At the stage of processing where the elog(ERROR) occurs,
do we still have access to the original query string?




pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2002-08-23 02:22:24
Subject: Re: Release of v7.2.2 (Was: Re: @(#)Mordred Labs ad...)
Previous:From: Lamar OwenDate: 2002-08-23 01:57:59
Subject: Re: My head is spinning

pgsql-patches by date

Next:From: Neil ConwayDate: 2002-08-23 02:33:00
Subject: more buffer paranoia
Previous:From: J. R. NieldDate: 2002-08-22 19:10:05
Subject: Fix for segfault in pgmodule.c: pgquery_dictresult()

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group