From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: oids on disk not in pg_class |
Date: | 2013-10-07 21:58:42 |
Message-ID: | D85E1E03-25A8-43A8-8D96-436DCEF56D87@blighty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Oct 7, 2013, at 2:48 PM, Guy Rouillier <guy(dot)rouillier(at)gmail(dot)com> wrote:
> We have a fairly large (1 TB) database we put on all SSDs because of a very high insert and update rate (). As our business has grown, we've been running into space constraints, so we went looking for files we might be able to delete.
>
> We found a large number (662 out of 1465 total ) and size (219 GB) of files in the data directory whose name does not correspond to an oid in the pg_class system catalog table. That amount of space would address our current space constraint problems. Some of these tables are recent (from today), while others are quite old (large volume in August and May, with some smaller ones as far back as February.
You need to be looking at pg_class.relfilenode, not pg_class.oid. They're often the same value, but often not.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-10-07 22:02:05 | Re: Altering parent table breaks child table defaults |
Previous Message | Guy Rouillier | 2013-10-07 21:48:34 | oids on disk not in pg_class |