Recovery Procedures in 'single user mode' ... - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Recovery Procedures in 'single user mode' ...
Date
Msg-id Pine.BSF.4.21.0009262323040.4209-100000@thelab.hub.org
Whole thread Raw
List pgsql-hackers
figuring I'd try out getting into the backend using postgres, to see if I
can 'bypass' some of the errors on those corrupted database, I'm wondering
if there is any way of taking what a 'select * from <table>' outputs:
        1: userid = "cibc001154"       (typeid = 1043, len = -1, typmod = 36, byval = f)        2: passwd = "INVALID"
(typeid= 1043, len = -1, typmod = 36, byval = f)        3: acct_type = "3"     (typeid = 23, len = 4, typmod = -1,
byval= t)       ----
 

and making it useful?  some way of using a simple postgres command to dump
the corrupted tables one by one?

thoughts?

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: ecpg is broken in current
Next
From: Hiroshi Inoue
Date:
Subject: Re: RE: [GENERAL] update inside transaction violates unique constraint?