From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: table size growing out of control |
Date: | 2002-07-17 17:01:21 |
Message-ID: | 3D35A2E1.26E6588D@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
>
> nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) writes:
> > On Wed, Jul 17, 2002 at 09:45:12AM -0400, Robert Treat wrote:
> >> ** with current_query blank I'm assuming we have nothing hanging around
> >> that would interfere right?. **
>
> > No, that could also indicate that either you're not the super-user, or you
> > haven't enabled stats_command_string in postgresql.conf
>
> > That probably isn't the best UI...
>
> Good point. What do people think of making the pg_stat_activity view do
> COALESCE(current_query, '<unknown>')
> so that there's a clear flag that you're not seeing anything?
Shouldn't be done on the view. The builtin function used to extract that
information from the stats file can do it much better. If memory serves
it's also the one who decides to return NULL if you're not a superuser.
So it could return <permission denied> or similar in that case to
distinguish.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-17 17:14:45 | Re: table size growing out of control |
Previous Message | GB Clark | 2002-07-17 16:37:53 | Re: Linux max on shared buffers? |