On Sunday 10 May 2009 15:32:26 Guillaume Smet wrote:
I attached a patch which allows to add the SQL state code into the
log_line_prefix. I used %e (as in error) as %s is already used.
Committed.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Fri, Jul 3, 2009 at 9:14 PM, Peter Eisentrautpete...@gmx.net wrote:
On Sunday 10 May 2009 15:32:26 Guillaume Smet wrote:
I attached a patch which allows to add the SQL state code into the
log_line_prefix. I used %e (as in error) as %s is already used.
Committed.
Thanks Peter.
--
Hi -hackers,
A customer of us recently wanted to separate user errors from system
errors as different teams are working on these 2 types of errors and
while they might want to ignore user errors (bad-written SQL queries
and so on), they want to be sure system errors are analyzed carefully.
A
On Sun, May 10, 2009 at 2:32 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
I attached a patch which allows to add the SQL state code into the
log_line_prefix. I used %e (as in error) as %s is already used.
Patch added to the next commit fest page.
--
Guillaume
--
Sent via pgsql-hackers
Guillaume Smet wrote:
Hi -hackers,
A customer of us recently wanted to separate user errors from system
errors as different teams are working on these 2 types of errors and
while they might want to ignore user errors (bad-written SQL queries
and so on), they want to be sure system errors are
On Sun, May 10, 2009 at 3:29 PM, Andrew Dunstan and...@dunslane.net wrote:
If we're going to do this I think it needs to be added to CSV log output
too.
AFAICS, it's already done for the CSV output hence my the only way to
have the SQL state in the *standard* log file.
Did I miss something?
Guillaume Smet wrote:
On Sun, May 10, 2009 at 3:29 PM, Andrew Dunstan and...@dunslane.net wrote:
If we're going to do this I think it needs to be added to CSV log output
too.
AFAICS, it's already done for the CSV output hence my the only way to
have the SQL state in the *standard*
Guillaume Smet guillaume.s...@gmail.com writes:
A customer of us recently wanted to separate user errors from system
errors as different teams are working on these 2 types of errors and
while they might want to ignore user errors (bad-written SQL queries
and so on), they want to be sure system
On Sun, May 10, 2009 at 4:07 PM, Tom Lane t...@sss.pgh.pa.us wrote:
This might or might not be worth doing, but it seems pretty nearly
entirely useless for the claimed purpose. What is your division between
user errors and system errors, and how will the SQLSTATE help you
make that?
We use
