Re: table size growing out of control

From: Robert Treat <rtreat(at)webmd(dot)net>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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:36:33
Message-ID: 1026920193.21424.91.camel@camel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Steve Brett 2002-07-17 15:50:50 just a quick one ...
Previous Message Tom Lane 2002-07-17 15:32:08 Re: timestamped archive data index searches