Received: from proxy1.tandy.com (proxy1.tandy.com [139.60.210.5]) by hub.org (8.9.3/8.9.3) with SMTP id PAA71440 for ; Mon, 10 Apr 2000 15:24:55 -0400 (EDT) (envelope-from JMaple1@Tandy.com) Received: from NTMAILGATE by proxy1.tandy.com via smtpd (for postgresql.org [216.126.84.28]) with SMTP; 10 Apr 2000 19:25:49 UT Received: by ntmailgate.tandy.com with Internet Mail Service (5.5.2650.21) id <2VV61YDR>; Mon, 10 Apr 2000 14:24:11 -0500 Message-ID: From: Jason Maples To: "'pgsql-admin@postgresql.org'" Subject: Database Recovery Date: Mon, 10 Apr 2000 14:24:17 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFA322.5870133E" X-Archive-Number: 200004/28 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFA322.5870133E Content-Type: text/plain; charset="iso-8859-1" I need help restoring a postgres database. My postgres server was destroyed by a tornado, but the raid drives containing the data are still intact. I built a new machine and mounted the raid drives, but I can't get the new installation of postgres to load the old databases. I get the " Database is not in pg-database" type of response. The old database config files, including the old pg_database file, are still inctact. Can I copy some of the old config files into the new postgres installation? Any ideas? ------_=_NextPart_001_01BFA322.5870133E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Database Recovery

I need help restoring a postgres database.=   My postgres server was destroyed by a tornado, but the raid drives c= ontaining the data are still intact.  I built a new machine and mounte= d the raid drives, but I can't get the new installation of postgres to load= the old databases.  I get the " Database is not in pg-database&q= uot; type of response.  The old database config files, including the o= ld pg_database file, are still inctact.  Can I copy some of the old co= nfig files into the new postgres installation?

Any ideas?


------_=_NextPart_001_01BFA322.5870133E--