From: | Riivo Kolka <riivo(dot)kolka(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Orphan table files at data/base/ |
Date: | 2024-02-28 13:44:47 |
Message-ID: | CAOZzBDgfO599erZrQsR6cXo4DbnSALDoAmEBVXDXcOFx_1E1og@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I was an unfortunate sequence of commands (all in single transaction)
DROP TABLE huge;
CREATE TABLE huge AS... (huge PostGIS ST_Union operation);
CREATE INDEX ON huge USING GIST (geometry);
by a well-meaning user, that caused a crash+recovery:
server process (PID 92411) was terminated by signal 9: Killed
terminating any other active server processes
all server processes terminated; reinitializing
database system was not properly shut down; automatic recovery in progress
And that left behind 280GB of files (of TABLE huge):
data/base/16384/2403959
...
data/base/16384/2403959.282
SELECT pg_filenode_relation(0,2403959);
-- returns NULL
may I do
sudo rm data/base/2403959*
?
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2024-02-28 14:12:44 | Re: PostgreSQL Guard |
Previous Message | Matthew Dennison | 2024-02-28 13:24:35 | RE: Unable to get PostgreSQL 15 with Kerberos (GSS) working |