Re: Overhead for stats_command_string et al, take 2

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Overhead for stats_command_string et al, take 2
Date: 2006-06-26 19:47:16
Message-ID: 200606261947.k5QJlG822878@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Oh, good point. Do we remove stats_command_string?
>
> You mean, remove the option to turn it off? I don't think so. Aside
> from whatever remaining overhead there is, there's a possible security
> argument to be made that one might not want one's commands exposed,
> even to other sessions with the same userid.

OK.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-06-26 19:57:31 Re: [COMMITTERS] pgsql: Change the row constructor syntax (ROW(...))
Previous Message Simon Riggs 2006-06-26 19:46:24 Re: "Truncated" tuples for tuple hash tables

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2006-06-26 20:12:55 Re: [PATCHES] Non-transactional pg_class, try 2
Previous Message Tom Lane 2006-06-26 19:10:03 Re: Overhead for stats_command_string et al, take 2