| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Recovery Procedures in 'single user mode' ... |
| Date: | 2000-09-27 02:25:25 |
| Message-ID: | Pine.BSF.4.21.0009262323040.4209-100000@thelab.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-09-27 05:34:43 | Re: RE: [GENERAL] update inside transaction violates unique constraint? |
| Previous Message | James Cribb | 2000-09-27 02:10:23 | \l+ dumps core |