| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Dolan, Sean" <sean(dot)dolan(at)lmco(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows! |
| Date: | 2023-03-16 19:24:49 |
| Message-ID: | 47d0b525ad3ba570b4100e7b8d2a2b002ceba232.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dolan, Sean | 2023-03-16 20:38:07 | Many logical replication synchronization worker threads kicking off for ONE table |
| Previous Message | Daniel Gustafsson | 2023-03-16 19:14:43 | Re: pg_upgrade Only the install user can be defined in the new cluster |