From: | "Wouter Sergeyssels" <Wouter(at)nucleus(dot)be> |
---|---|
To: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: recover in single-user backend fails |
Date: | 2008-09-08 10:34:13 |
Message-ID: | 18834F5BEC10824891FB8B22AC821A5A1DC749@nucleus-srv01.Nucleus.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hey Guys,
Thanks for your input. Meanwhile we have recovered from a backup.
Lesson of all this, upgrade asap to postgres 8.2?
Thanks,
WS.
-----Original Message-----
From: Greg Stark [mailto:greg(dot)stark(at)enterprisedb(dot)com] On Behalf Of
Gregory Stark
Sent: zondag 7 september 2008 11:50
To: Tom Lane
Cc: Wouter Sergeyssels; pgsql-general(at)postgresql(dot)org
Subject: Re: recover in single-user backend fails
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> The only recovery strategy that I can think of in 8.1 is to blow away
> your WAL with pg_resetxlog, let the database come up in a damaged
> condition, and then try to extract data from it.
Would it work if he rebuilt 8.1 with a "return;" as the first line of
gist_redo() in gistxlog.c and when recovery (hopefully) completes
immediately
drop any gist indexes?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Cai | 2008-09-08 10:38:06 | Re: Very weird problem of "order by" in postgresql |
Previous Message | Ivan Zolotukhin | 2008-09-08 09:46:01 | 8.3 on FreeBSD 6.3, sudden performance degradations |