Re: Overhead for stats_command_string et al, take 2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(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:10:03
Message-ID: 15980.1151349003@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2006-06-26 19:46:24 Re: "Truncated" tuples for tuple hash tables
Previous Message Bruce Momjian 2006-06-26 19:07:30 Re: Overhead for stats_command_string et al, take 2

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-06-26 19:47:16 Re: Overhead for stats_command_string et al, take 2
Previous Message Bruce Momjian 2006-06-26 19:07:30 Re: Overhead for stats_command_string et al, take 2