From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Lists <lists(at)benjamindsmith(dot)com> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Postgresql Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Unexpectedly high disk space usage |
Date: | 2012-11-06 19:11:49 |
Message-ID: | CAMkU=1zewuuCk4x1ibYtJaX7O5NJUODOSG=zDrzjS1i_YL21rw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Nov 6, 2012 at 10:49 AM, Lists <lists(at)benjamindsmith(dot)com> wrote:
> I followed your example, the result is at the bottom. Based on this it would
> seem that there are 3-4 databases that seem to be the culprit. How could I
> get more depth/detail on what specifically is the problem?
If you have installed the contrib modules (oid2name specifically), you
can use that to get the name of the bloated database:
oid2name | fgrep 607471
If the name of the database doesn't give you any insight, then look
for large files in the directory base/607471 that whose names all
start with the same digits and use oid2name to get the names of the
relations for those files.
oid2name -d <name of database> -o <base name of large files>
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-11-06 19:28:51 | Re: Unexpectedly high disk space usage |
Previous Message | Lists | 2012-11-06 18:49:38 | Re: Unexpectedly high disk space usage |