BTom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Yes, I do. I have applied the attached patch to fix this issue and > > several others. The fix was to save the bind parameters in the portal, > > and display those in the executor output, if available. > > I have a feeling you just blew away the 4% savings in psql I've spent > the evening on. What's the overhead of this patch?
The only overhead I see is calling log_after_parse() all the time, rather than only when log_statement is all. I could fix it by checking log_statement and log_min_duration_statement >= 0. Does log_after_parse() look heavy to you? -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
