| From: | Philip Semanchuk <philip(at)americanefficient(dot)com> |
|---|---|
| To: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com> |
| Cc: | Mikael Petterson <mikaelpetterson(at)hotmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Disk is filling up with large files. How can I clean? |
| Date: | 2024-10-09 13:02:38 |
| Message-ID: | D816802A-38F4-4402-A542-063DF5BB5648@americanefficient.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Oct 9, 2024, at 5:52 AM, Torsten Förtsch <tfoertsch123(at)gmail(dot)com> wrote:
>
> Filenames like 16665, 16665.1, 16665.2 etc all represent the same table (or similar). The number 16665 is called the file node.
>
> To get a list of file nodes for a specific database you can run:
>
> SELECT oid::regclass::text, relfilenode FROM pg_class;
>
> The /16384/ in the path represents the database. To decipher that you can run:
>
> SELECT datname, oid FROM pg_database;
>
> Once you have all that information, you know which database to connect to and which tables are big. Then you can DROP/DELETE/TRUNCATE or so.
Mikael, if you’re unaware of VACUUM FULL (as opposed to just VACUUM), you should read about that too.
Hope that helps,
Philip
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-10-09 14:25:16 | Re: pg_dump throwing segfault error during backup |
| Previous Message | iseki zero | 2024-10-09 10:07:09 | Questions about document "Concurrenry control" section |