Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id AA054650176
	for <pgsql-admin-postgresql.org@postgresql.org>;
	Sat, 23 Aug 2008 02:22:42 -0300 (ADT)
Received: from postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 48791-07 for <pgsql-admin-postgresql.org@postgresql.org>;
	Sat, 23 Aug 2008 02:22:33 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from smtp.01.com (lb-2.01.com [38.98.186.147])
	by postgresql.org (Postfix) with ESMTP id 6B853650177
	for <pgsql-admin@postgresql.org>; Sat, 23 Aug 2008 02:22:31 -0300 (ADT)
Received: from asav-1.01.com (localhost.localdomain [127.0.0.1])
	by asav-1.01.com (8.13.1/8.13.1) with SMTP id m7N5MLcP027237;
	Sat, 23 Aug 2008 00:22:22 -0500
Received: from smtp-1.01.com (smtp-1.01.com [38.98.186.157])
	by asav-1.01.com (asav-1.01.com [10.25.1.11])
	id k7M0ML0518634980Q2 ret-id none; Sat, 23 Aug 2008 00:22:22 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp-1.01.com (Postfix) with ESMTP id BD890E0CA2;
	Sat, 23 Aug 2008 00:22:21 -0500 (CDT)
Received: from smtp-1.01.com ([127.0.0.1])
	by localhost (smtp-1.01.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cwPeKNxARh7s; Sat, 23 Aug 2008 00:22:21 -0500 (CDT)
Received: from [192.168.1.104] (unknown [76.194.27.53])
	by smtp-1.01.com (Postfix) with ESMTP id 48964E0C8D;
	Sat, 23 Aug 2008 00:22:21 -0500 (CDT)
Message-ID: <48AF9E8B.9020508@frostconsultingllc.com>
Date: Fri, 22 Aug 2008 22:22:19 -0700
From: Jeff Frost <jeff@frostconsultingllc.com>
Organization: Frost Consulting, LLC
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Tena Sakai <tsakai@gallo.ucsf.edu>
CC: pgsql-admin@postgresql.org
Subject: Re: restoring from dump
References: <FE44E0D7EAD2ED4BB2165071DB8E328C0378F40C@egcrc-ex01.egcrc.org>
	<Pine.LNX.4.64.0808221515340.14879@discord.home.frostconsultingllc.com>
	<FE44E0D7EAD2ED4BB2165071DB8E328C0378F40D@egcrc-ex01.egcrc.org>
	<Pine.LNX.4.64.0808221553290.14879@discord.home.frostconsultingllc.com>
	<FE44E0D7EAD2ED4BB2165071DB8E328C0378F40F@egcrc-ex01.egcrc.org>
	<FE44E0D7EAD2ED4BB2165071DB8E328C0378F413@egcrc-ex01.egcrc.org>
	<Pine.LNX.4.64.0808222125160.14696@glacier.frostconsultingllc.com>
	<FE44E0D7EAD2ED4BB2165071DB8E328C0378F414@egcrc-ex01.egcrc.org>
In-Reply-To: <FE44E0D7EAD2ED4BB2165071DB8E328C0378F414@egcrc-ex01.egcrc.org>
Content-Type: multipart/alternative;
	boundary="------------010405070900060001030008"
X-FSL-MailScanner-Information: Please contact postmaster@01.com for more
	information
X-FSL-MailScanner: Found to be clean
X-FSL-MailScanner-SpamCheck: 
X-FSL-MailScanner-From: jeff@frostconsultingllc.com
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.001 tagged_above=0 required=5
	tests=HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 200808/137
X-Sequence-Number: 29982

This is a multi-part message in MIME format.
--------------010405070900060001030008
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Tena Sakai wrote:
>
> > If you want to restore all the databases that were in this
> > postgresql installation at the time of the backup, then the
> > best thing to do is drop all those DBs before attempting the
> > restore.
> Yes, the database in question is built and updated continuously
> from a several sources.  There was a massive power failure,
> a series of them, and things got to be a very inconsistent
> state and therefore we need to go back to a reliable, trustworthy
> backup and then rebuild from there.
>
> What I gather, from your comments, all I have to do would to issue
> a psql command:
>   drop database <dbname>
> then repeat what I did from shell prompt, ie.,
>   zcat <compressed_file> | psql postgres > restore.out 2 > restore.err
>
> Would you mind confirming if I am understanding you correctly?
>
Yes, based on the information you've given us, you should be able to
restore the entire database (and any other databases that were in the
cluster) by first dropping those databases and then issuing the above
command.

BTW, if you find yourself with an older version of postgresql, this
could be a good opportunity to upgrade.  I'm not sure if you mentioned
what version you were using in your original post.



-- 
Jeff Frost, Owner 	<jeff@frostconsultingllc.com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 916-647-6411	FAX: 916-405-4032


--------------010405070900060001030008
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tena Sakai wrote:
<blockquote
 cite="mid:FE44E0D7EAD2ED4BB2165071DB8E328C0378F414@egcrc-ex01.egcrc.org"
 type="cite">
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta name="Generator"
 content="MS Exchange Server version 6.5.7652.24">
  <title>RE: [ADMIN] restoring from dump</title>
<!-- Converted from text/plain format -->
  <p><font size="2">&gt; If you want to restore all the databases that
were in this<br>
&gt; postgresql installation at the time of the backup, then the<br>
&gt; best thing to do is drop all those DBs before attempting the<br>
&gt; restore.<br>
Yes, the database in question is built and updated continuously<br>
from a several sources.&nbsp; There was a massive power failure,<br>
a series of them, and things got to be a very inconsistent<br>
state and therefore we need to go back to a reliable, trustworthy<br>
backup and then rebuild from there.<br>
  <br>
What I gather, from your comments, all I have to do would to issue<br>
a psql command:<br>
&nbsp; drop database &lt;dbname&gt;<br>
then repeat what I did from shell prompt, ie.,<br>
&nbsp; zcat &lt;compressed_file&gt; | psql postgres &gt; restore.out 2 &gt;
restore.err<br>
  <br>
Would you mind confirming if I am understanding you correctly?<br>
  <br>
  </font></p>
</blockquote>
Yes, based on the information you've given us, you should be able to
restore the entire database (and any other databases that were in the
cluster) by first dropping those databases and then issuing the above
command.<br>
<br>
BTW, if you find yourself with an older version of postgresql, this
could be a good opportunity to upgrade.&nbsp; I'm not sure if you mentioned
what version you were using in your original post.<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
Jeff Frost, Owner 	<a class="moz-txt-link-rfc2396E" href="mailto:jeff@frostconsultingllc.com">&lt;jeff@frostconsultingllc.com&gt;</a>
Frost Consulting, LLC 	<a class="moz-txt-link-freetext" href="http://www.frostconsultingllc.com/">http://www.frostconsultingllc.com/</a>
Phone: 916-647-6411	FAX: 916-405-4032
</pre>
</body>
</html>

--------------010405070900060001030008--