[SQL] Finding context for error log

2006-09-26 Thread Kyle Bateman
I get the following message in my postgres log: ERROR: 42601: syntax error at or near "%" at character 269 LOCATION: yyerror, scan.l:761 I have a fairly complex schema (lots of database objects) and many users hitting the db with lots of connections, so I'm not really sure what bit of code i

Re: [SQL] Finding context for error log

2006-09-26 Thread Tom Lane
Kyle Bateman <[EMAIL PROTECTED]> writes: > Is there an easy way to get postgres to > spit out the SQL statement it was parsing when it generated the error? "log_min_error_statement = error" is what you're looking for. regards, tom lane ---(end of

Re: [SQL] Finding context for error log

2006-09-26 Thread Vivek Khera
On Sep 26, 2006, at 10:56 AM, Tom Lane wrote: "log_min_error_statement = error" is what you're looking for. my personal belief is that this should be the default, as the current default (essentially "never") is mostly useless. smime.p7s Description: S/MIME cryptographic signature