Applied. ---------------------------------------------------------------------------
Bruce Momjian wrote: > Tom Lane wrote: > > Bruce Momjian <[EMAIL PROTECTED]> writes: > > > Seeing stats_command_string with almost zero overhead is great news! > > > Should we remove that setting and just have it enabled all > > > the time? > > > > If you don't need it, you shouldn't have to pay any overhead for it, > > I think. One could make an argument now for having stats_command_string > > default to ON, though. > > The attached patch makes stats_command_string default to 'on', and > updates the documentation. > > > Something that might also be interesting is an option to suppress > > per-command ps_status reporting. On machines where updating ps status > > takes a kernel call, there's now a pretty good argument why you might > > want to turn that off and rely on pg_stat_activity instead. > > OK, can I get a timing report from someone with the title on/off that > shows a difference? > > -- > 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 -- 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 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
