Search Postgresql Archives

Re: Disk is filling up with large files. How can I clean?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 9, 2024 at 9:02 AM Philip Semanchuk <philip@xxxxxxxxxxxxxxxxxxxxx> wrote:

> On Oct 9, 2024, at 5:52 AM, Torsten Förtsch <tfoertsch123@xxxxxxxxx> 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.

VACUUM FULL with an almost-full disk probably isn't the wisest idea.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> crustacean!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux