Tom,
I was able to locate a bad reporting program (apparently the pg update to 7.4 caused some mismatched datatypes, i
believe,from the logs.) that was causing this.
I will look into pg_class for the relfilenode 17610 and others to see if i can free up the space already taken up...
Thanks,
Anjan
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Fri 12/26/2003 6:29 PM
To: Anjan Dave
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Database taking up space rapidly
"Anjan Dave" <adave@vantage.com> writes:
> Here's where I find the bulk of the large files:
> -rw------- 1 postgres postgres 1073741824 Dec 23 18:57 17610
> -rw------- 1 postgres postgres 1073741824 Dec 23 22:41 17610.1
> [ etc ]
So, which table or index has relfilenode 17610 (look in pg_class)?
What sorts of operations are you doing on it?
> Not sure what's going on here...also vacuum analyzed the db a few
> minutes ago.
The question is more like how often do you run vacuum. You probably
need more frequent routine vacuumings, larger FSM settings, or a
combination.
regards, tom lane
