Re: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows! - Mailing list pgsql-general

From Laurenz Albe
Subject Re: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows!
Date
Msg-id 47d0b525ad3ba570b4100e7b8d2a2b002ceba232.camel@cybertec.at
Whole thread Raw
In response to RE: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows!  ("Dolan, Sean" <sean.dolan@lmco.com>)
Responses Many logical replication synchronization worker threads kicking off for ONE table  ("Dolan, Sean" <sean.dolan@lmco.com>)
Re: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows!  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
List pgsql-general
On Thu, 2023-03-16 at 13:20 +0000, Dolan, Sean wrote:
> I messed up and confused issues.   The error is : 
> ERROR: Could not extend pg_tblspc/16555/PG_13_20200/xxxx/xxxx  No space left on device
> HINT: Check free disk space
>
> So the schema is "full" and the offender is this one table.
> I can't TRUNCATE as there needs to be space to perform the action.
> Is there a way to see if there is a transaction on that table like you allude to?

Ah, that's different.

If you don't have enough space to run TRUNCATE, and you don't feel like
extending the disk space, DROP TABLE would be a convenient alternative.

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: pg_upgrade Only the install user can be defined in the new cluster
Next
From: "Dolan, Sean"
Date:
Subject: Many logical replication synchronization worker threads kicking off for ONE table