Re: [HACKERS] log_error_verbosity and unexpected errors

2014-07-04 Thread Oskari Saarenmaa
On 02/07/14 22:10, Tom Lane wrote: Greg Stark st...@mit.edu writes: I think log_error_verbosity is a strange variable. It's useless for expected user-facing errors but essential for unexpected errors that indicate bugs in the code -- and you can only have it on for everything or off for

[HACKERS] log_error_verbosity and unexpected errors

2014-07-02 Thread Greg Stark
I think log_error_verbosity is a strange variable. It's useless for expected user-facing errors but essential for unexpected errors that indicate bugs in the code -- and you can only have it on for everything or off for everything. I'm finding I usually want it set to 'verbose' for anything that

Re: [HACKERS] log_error_verbosity and unexpected errors

2014-07-02 Thread Tom Lane
Greg Stark st...@mit.edu writes: I think log_error_verbosity is a strange variable. It's useless for expected user-facing errors but essential for unexpected errors that indicate bugs in the code -- and you can only have it on for everything or off for everything. I'm finding I usually want

Re: [HACKERS] log_error_verbosity and unexpected errors

2014-07-02 Thread Merlin Moncure
On Wed, Jul 2, 2014 at 2:10 PM, Tom Lane t...@sss.pgh.pa.us wrote: Greg Stark st...@mit.edu writes: I think log_error_verbosity is a strange variable. It's useless for expected user-facing errors but essential for unexpected errors that indicate bugs in the code -- and you can only have it on

Re: [HACKERS] log_error_verbosity and unexpected errors

2014-07-02 Thread Tom Lane
Merlin Moncure mmonc...@gmail.com writes: Not trying to hijack your thread, just wondering out load if a SQLSTATE driven verbosity decision, if you were to do that, could/should also be hooked to client console logging and/or psql. Yeah, you could certainly argue that a similar facility on the