From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: table size growing out of control |
Date: | 2002-07-17 15:28:50 |
Message-ID: | 200207171528.g6HFSoa07300@candle.pha.pa.us |
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?
>
> I'm not wedded to the particular string <unknown>, if someone has a
> better idea.
Yes, we really should report something on all the stats tables when they
aren't enabled. Would safe a lot of headaches.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-17 15:32:08 | Re: timestamped archive data index searches |
Previous Message | Tom Lane | 2002-07-17 15:22:24 | Re: OIDs (Or: another RTFM question?) |