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

From Jan Wieck
Subject Re: table size growing out of control
Date
Msg-id 3D357FBE.56ACBFB9@Yahoo.com
Whole thread Raw
In response to table size growing out of control  (Robert Treat <rtreat@webmd.net>)
Responses Re: table size growing out of control
List 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@Yahoo.com #

pgsql-general by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: PostgreSQL in mission-critical system
Next
From: nconway@klamath.dyndns.org (Neil Conway)
Date:
Subject: Re: table size growing out of control