From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kevin Brown <kevin(at)sysexperts(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: stats_command_string default? |
Date: | 2003-02-14 21:51:14 |
Message-ID: | 11351.1045259474@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Kevin Brown <kevin(at)sysexperts(dot)com> writes:
> Would it make more sense to enable stats_command_string by default?
I'd vote against it. If we turn it on by default, people are paying
for a feature they may not even know exists. Once they find out about
it and decide they want it, they can turn it on easily enough.
If you can show that the overhead is unmeasurable, that'd indicate that
this argument is bogus; but I suspect it's not negligible, at least on
simple queries.
> It would also be handy if users could see their own queries while the
> rest remain blank. That would require changing
> pg_stat_get_backend_activity() so that it returns a value if the user
> is the superuser or if the user asking for the answer is the same as
> the user who owns the backend entry being looked up. Are there any
> pitfalls to implementing that?
Seems reasonable offhand ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tilo Schwarz | 2003-02-14 21:55:51 | Re: Changing the default configuration (was Re: [pgsql-advocacy] |
Previous Message | Bruce Momjian | 2003-02-14 20:53:45 | Re: location of the configuration files |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-14 21:59:33 | Re: Cosmetic change in catalog/index.c |
Previous Message | Bruce Momjian | 2003-02-14 19:53:12 | Re: fix regression in .pgpass handling |