URGENT: Need to recover overwritten data from dead tuples
🔢DB Connections🤷other🟢SQL
URGENT: Need to recover overwritten data from dead tuples — Project duzjtajdoptwtxwolhor
A stale browser session auto-saved old data over a newer version of a row in my electrical_mappings table. The previous data is confirmed still on disk as dead tuples:
- Main table: 3 dead tuples (n_dead_tup = 3, last_autovacuum = NULL)
- TOAST table: 324 dead chunks
- Autovacuum disabled on the table to preserve them
I need to read the previous wizard_data (JSONB) for row 45ec7053-da76-4ebc-884c-d04ac1a58752.
I can't install pageinspect or pg_surgery — both blocked by supautils. pg_walinspect is installed but PG15 doesn't expose block data. I've tried every approach I can think of from the postgres role.
Is there any way to read dead tuples on Supabase without superuser? Or can a Supabase team member run a pageinspect query on my behalf?
Support ticket: SU-342166
Plan: Pro
A stale browser session auto-saved old data over a newer version of a row in my electrical_mappings table. The previous data is confirmed still on disk as dead tuples:
- Main table: 3 dead tuples (n_dead_tup = 3, last_autovacuum = NULL)
- TOAST table: 324 dead chunks
- Autovacuum disabled on the table to preserve them
I need to read the previous wizard_data (JSONB) for row 45ec7053-da76-4ebc-884c-d04ac1a58752.
I can't install pageinspect or pg_surgery — both blocked by supautils. pg_walinspect is installed but PG15 doesn't expose block data. I've tried every approach I can think of from the postgres role.
Is there any way to read dead tuples on Supabase without superuser? Or can a Supabase team member run a pageinspect query on my behalf?
Support ticket: SU-342166
Plan: Pro
