> These are both logged as ERROR: which is easy to check for with
> automatic monitoring. However I wouldn't want to be called out to fix
> a non-existent error where someone has typed in some nonsense. Is it
> easy to suppress the syntax errors so that the real database errors
> are obvious?
I think the short answer is "No", unless you do your own
post-processing. But note that syntax errors may also point to
mistakes in your application code.
If you want to filter out randomness that occurs during interactive
sessions, I'd rather attack the problem there. You could, for example,
alter the logging settings in your .psqlrc file.
In response to
pgsql-admin by date
|Next:||From: Erika Terahata Torres Prada e Silva - MPS||Date: 2006-08-17 21:05:53|
|Subject: RES: RES: Issue on Varchar Ordering|
|Previous:||From: Peter Eisentraut||Date: 2006-08-17 16:15:08|
|Subject: Re: RES: Issue on Varchar Ordering|