Free project stuck in recovery after disk full — is Pause/Resume safe?

[rgzpkb26vn-code]

My free project is down and I cannot reach the database at all.

Project: iljpbwmdkfkskbbsomqu (eu-west-1, Free plan, Nano compute)

Postgres is running but never finishes recovery:

FATAL: 57P03: the database system is not accepting connections
DETAIL: Hot standby mode is disabled.

• PostgREST returns 503 PGRST002 ("Could not query the database for
  the schema cache")
• Port 5432 refuses connections
• The dashboard cannot read the Postgres version
• Disk was 1.92 GB / 2 GB when it went down
• Restarting the project did not help
• Automatic disk expansion never fired

Cause is known: I bulk-loaded a public reference dataset into ONE table
(public.parcelles_personnes_morales) and filled the volume. WAL replay
cannot complete because there is no free space left to write to.

MY MAIN QUESTION, for anyone who has been through this:
Is it safe to Pause and then Resume the project in this state? Does a
Resume restore from a logical backup (which would come back compacted,
without the WAL backlog and dead tuples), or does it restore the same
full volume as-is? If it is the second, pausing gains me nothing and
risks the data, so I would rather not try it blindly.

FOR THE SUPABASE TEAM, if someone sees this — either of these fixes it:

1. Temporarily grow the volume so recovery can complete. I will
   TRUNCATE that table within minutes and the space comes straight
   back — my own data is under 100 MB.
2. Or run this single statement for me:
   TRUNCATE public.parcelles_personnes_morales;

I have sent two support emails with no reply yet. I am not asking for
free resources, just for one write so the instance can start again.

[GaryAustin1]

Pause/Restore is safe as far as data loss goes.
But it could hang because it can't do a backup then support would be required (which it likely is right now).
The only other thing would be to make sure your app is not looping on errors still hitting the REST API or DB.
Free plans don't have disk expansion that I know of.