I also forgot to mention, vacuumdb fails on the command line now with
the following error:
vacuumdb: could not connect to database smt: FATAL: sorry, too many
clients already
On Apr 23, 2005, at 9:57 AM, Richard Plotkin wrote:
> If anybody has additional advice on this problem, I would really,
> really appreciate it...
>
> I updated postgres to 8.0.2, am running vacuumdb -faz every 3 hours,
> and 50 minutes after a vacuum the CPU usage still skyrocketed, and the
> disk started filling. This time, there is only a single file that is
> spanning multiple GB, but running oid2name again returns no result on
> the oid or filenode.
>
> With the increased vacuuming, fixed temp tables, etc., I really am at
> a loss for what's happening, and could really use some additional
> help.
>
> Thank you,
> Richard
>
