Re: table size growing out of control - Mailing list pgsql-general

From Robert Treat
Subject Re: table size growing out of control
Date
Msg-id 1026920193.21424.91.camel@camel
Whole thread Raw
In response to Re: table size growing out of control  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: table size growing out of control
List pgsql-general
On Wed, 2002-07-17 at 10:31, Jan Wieck wrote:
> Robert Treat wrote:
> >
> > those are the ways I had been thinking, here are some results:
> >
> > rms=# select * from pg_stat_activity;
> >   datid   | datname | procpid | usesysid | usename  | current_query
> > ----------+---------+---------+----------+----------+---------------
> > 11914305 | rms     |    2355 |        1 | postgres |
> > 11914305 | rms     |   29985 |        1 | postgres |
> >
> > [...]
> >
> > ** with current_query blank I'm assuming we have nothing hanging around
> > that would interfere right?. **
>
> Assuming that you are doing it as a database superuser, wrong. It means
> that your have "stats_command_string = false" or commented out in your
> postgresql.conf file. Otherwise it would report "<IDLE>" or "<IDLE> in
> transaction".
>

ok. but my ps aux | grep postgres did label all connections as idle,
which should be equivalent, right?

Robert Treat


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: timestamped archive data index searches
Next
From: Steve Brett
Date:
Subject: just a quick one ...