Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Are people going to be happy that log_statement and > > log_min_duration_statement output the statement twice? > > If those are the only cases you're worried about, a far simpler solution > is to clear debug_query_string before instead of after emitting those > log messages.
I am concerned about setting debug_query_string to NULL, calling ereport(), and then resetting it might cause problems because of cases where ereport might want to access debug_query_string for other uses, for cases where ereport doesn't return to the reset code (but I assume that is handled), and for cases like pgmonitor that would stop a backend, read debug_query_string, and disconnect. I can create a global variable to control this, but the new elog level seemed cleaner. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
