Andrew Dunstan wrote:
Or I would do except that I see that a parse error causes a longjmp out of that code. I will see if I can come up with a way around that. If not, I think we'd better let sleeping dogs lie.
Actually, I think I can improve the present situation. Currently, if log_statement is not turned on and you send a query that doesn't parse, all you get is the error trace. By deferring it till right after the parse we can force logging of the query string on a parse error, regardless of that setting (which seems to me to be a very desirable outcome). The only thing is that you will get the error trace first (because it comes from the parser) rather than the query string first.
cheers
andrew
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
