Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 26 Jun 2006 15:47:16 -0400 (EDT)
- Message-id: <200606261947(dot)k5QJlG822878(at)momjian(dot)us>
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. +
- References:
- Re: Overhead for stats_command_string et al, take 2
- From: Tom Lane
- Re: Overhead for stats_command_string et al, take 2
- Prev by Date: Re: "Truncated" tuples for tuple hash tables
- Next by Date: Re: [PATCHES] Non-transactional pg_class, try 2
- Previous by thread: Re: Overhead for stats_command_string et al, take 2
- Next by thread: UTF8 server-side on Win32?
- Indexes: