On Fri, Jul 3, 2009 at 9:14 PM, Peter Eisentraut 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.
--
Guillaume
--
S
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 sub
On Sun, May 10, 2009 at 4:07 PM, Tom Lane 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 http://www.p
Guillaume Smet 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 errors are analyzed
Guillaume Smet wrote:
On Sun, May 10, 2009 at 3:29 PM, Andrew Dunstan 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 mi
On Sun, May 10, 2009 at 3:29 PM, Andrew Dunstan 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?
Thanks for your f
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 a
On Sun, May 10, 2009 at 2:32 PM, 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.
Patch added to the next commit fest page.
--
Guillaume
--
Sent via pgsql-hackers mailing list (pgsql-ha
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 good