Bring to dead tuples to alive - Mailing list pgsql-sql

From Roberto Médola
Subject Bring to dead tuples to alive
Date
Msg-id CANRMYmg3ihZz_-jY3MN7Stz9p9wnL399TNJRduBv6xpBbZdTuQ@mail.gmail.com
Whole thread Raw
Responses Re: Bring to dead tuples to alive  (Steve Midgley <science@misuse.org>)
List pgsql-sql
Hi.
I need to revert someone deletes in my table.
I researched a lot and found pg_dirtyread and also pgtreats. Unfortunately I was unable to use either. My base is on a windows 2008 r2, PostgreSQL 9.3.5 and is over 4 TB in size. The table in question is distributed through tablespace in several units, inheriting to keep the records together.
Fortunately for me, this base does not delete, just insert and the deletes that were done wrong, were executed by me.
It turns out that I simulated on another server (linux) a table with fields similar to those of production and I couldn't see the dead tuples because of one of the fields being bytea.
Already tried:
 - pg_dirtyread
 - compile the sources to show the HeapTupleSatisfiesVisibility
But as the server is on windows, compilation is very complicated.

Does anyone have any suggestions on how I can reverse the deletes?

pgsql-sql by date:

Previous
From: Mohamed Wael Khobalatte
Date:
Subject: Re: Non blocking type change for primary column
Next
From: Steve Midgley
Date:
Subject: Re: Bring to dead tuples to alive