Re: table size growing out of control

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Robert Treat <rtreat(at)webmd(dot)net>
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 14:31:26
Message-ID: 3D357FBE.56ACBFB9@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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".

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 #

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message stefan 2002-07-17 14:33:17 Re: sequence id
Previous Message Andrew Sullivan 2002-07-17 14:17:17 Re: PostgreSQL in mission-critical system