pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Martijn van Oosterhout <kleptog@svana.org>
To: Mark Holm <markh@infoarch.com>
Cc: pgsql-jobs@postgresql.org
Cc: pgsql-admin@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] PGSQL Database Recovery in Portland Oregon Area needed ASAP
Date: Thu, 18 May 2006 07:39:45 +0200
Message-ID: <20060518053945.GB32755@svana.org> (raw)
In-Reply-To: <4534BE485054BA4B95D3F3479C7B1BEE0EE5AF@infoarch-sbs.InfoArchInc.local>
References: <4534BE485054BA4B95D3F3479C7B1BEE0EE5AF@infoarch-sbs.InfoArchInc.local>

On Tue, May 16, 2006 at 09:53:54AM -0700, Mark Holm wrote:
> I have a client that is running an older version of Lyris List
> Manager against PostGres 7.1.2, that has crashed their database
> beyond my ability to recover it. The error that I am getting when we
> try and restart the database is:

Very old database, consider upgrading.

> I have gone through the stuff on-line concerning this error and
> attempted to reinitialize the database and restore the night before's
> backup, but apparently the backups were not quite setup correctly as
> I cannot get a valid restore either. I am out of my depth on this one
> and am willing to contract somebody to help get this database back
> on-line again ASAP, as the client is getting frantic. If you have
> proven experience doing this sort of recovery, please contact me at
> the number or email address below. I am not a member of the lists, so
> please contact me directly. Rates are negotiable, but I will have to
> clear them with client before we proceed.

Make sure you have a physical backup. pg_resetxlog may get you far
enough to start the server. Them immediatly dump, destroy the cluster
and restore. pg_resetxlog solves some problems, but you can't guarentee
your integrity anymore...

Have a ncie day,
-- 
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachments:

  signature.asc (application/pgp-signature, 188B) download

view thread (2+ messages)

Message-ID: <20060518053945.GB32755@svana.org>
Permalink:  ../20060518053945.GB32755@svana.org/
Also on:    postgresql.org/message-id/20060518053945.GB32755@svana.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: kleptog@svana.org, markh@infoarch.com, pgsql-jobs@postgresql.org, pgsql-general@postgresql.org
  Subject: Re: [GENERAL] PGSQL Database Recovery in Portland Oregon Area needed ASAP
  In-Reply-To: <20060518053945.GB32755@svana.org>
  References: <4534BE485054BA4B95D3F3479C7B1BEE0EE5AF@infoarch-sbs.InfoArchInc.local> <20060518053945.GB32755@svana.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox