From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Data recovery after inadvertent update? |
Date: | 2012-09-18 09:10:54 |
Message-ID: | 50583A9E.10208@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi all
Someone on SO has UPDATEd away some data they cared about. I've written
a bit on what they might want to do, but really don't know enough, so I
was hoping for some aid/ideas. In particular, is the advice to use "
pg_ctl stop -m immediate" (to hopefully avoid a checkpoint) appropriate
and useful? I'm just not sure.
Also, are there any functions to read raw tuple bytes to `RECORD's? I
couldn't find any in `pageinspect', `pgstattuple', `adminpack', etc. Am
I right in guessing that they're pretty much going to require hand data
recovery or the use of some custom C extension code to get at the data -
if it still exists?
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2012-09-18 09:34:59 | Re: foreign key from array element |
Previous Message | Rafal Pietrak | 2012-09-18 08:29:36 | Re: RFE: Column aliases in WHERE clauses |