/usr/local/pgsql/data/base/17234/42791
/usr/local/pgsql/data/base/17234/42791.1
/usr/local/pgsql/data/base/17234/42791.2
/usr/local/pgsql/data/base/17234/42791.3
/usr/local/pgsql/data/base/17234/42791.4
/usr/local/pgsql/data/base/17234/42791.5
/usr/local/pgsql/data/base/17234/42791.6
/usr/local/pgsql/data/base/17234/42791.7
/usr/local/pgsql/data/base/17234/42791.8
/usr/local/pgsql/data/base/17234/42791.9
/usr/local/pgsql/data/base/17234/42791.10
/usr/local/pgsql/data/base/17234/42791.11
On Apr 23, 2005, at 11:06 AM, Tom Lane wrote:
> Richard Plotkin <richard@richardplotkin.com> writes:
>> 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.
>
> What is the filename exactly (full path)?
>
> regards, tom lane
>