Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 696544759AF for ; Fri, 16 Aug 2002 11:00:38 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id BC1444758D7 for ; Fri, 16 Aug 2002 11:00:37 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g7GF0gVk007866; Fri, 16 Aug 2002 11:00:42 -0400 (EDT) To: Jodi Kanter Cc: Postgres Admin List Subject: Re: upgrade issue In-reply-to: <00fd01c24532$27600240$de138f80@virginia.edu> References: <00fd01c24532$27600240$de138f80@virginia.edu> Comments: In-reply-to Jodi Kanter message dated "Fri, 16 Aug 2002 10:35:22 -0400" Date: Fri, 16 Aug 2002 11:00:41 -0400 Message-ID: <7865.1029510041@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/195 X-Sequence-Number: 5310 Jodi Kanter writes: > I have now read (all be it to late) the documentation warning of this > problem. Luckily we do not have any data that I need to save in the > database. I could easily get back to a functioning state if I could drop the > database and rebuild it via my schema.sql file. However, I cannot drop the > database unless I can get the postmaster started. If you don't need any of the data then you can just rm -rf $PGDATA and initdb. (You might at least want to save the text configuration files that appear in the top level $PGDATA directory, however, as consulting them will make it easier to configure your new installation.) regards, tom lane