Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E06DF64FD0A for ; Wed, 17 Sep 2008 18:33:34 -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 35645-05 for ; Wed, 17 Sep 2008 18:33:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id CB40B64FCED for ; Wed, 17 Sep 2008 18:33:31 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m8HLXRjK028143; Wed, 17 Sep 2008 17:33:27 -0400 (EDT) To: Daniel Christopher cc: Jonathan Nalley , pgsql-admin@postgresql.org Subject: Re: unable to backup database -- psql not up to date In-reply-to: <48D14EA7.5070802@gmail.com> References: <19520466.post@talk.nabble.com> <48D14EA7.5070802@gmail.com> Comments: In-reply-to Daniel Christopher message dated "Wed, 17 Sep 2008 11:38:31 -0700" Date: Wed, 17 Sep 2008 17:33:27 -0400 Message-ID: <28142.1221687207@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/187 X-Sequence-Number: 30280 Daniel Christopher writes: > I compiled from source, and followed the instructions in the > documentation about upgrading to a new major release (pg_dumpall, > shutdown, mv old version, install new version, restore) Well, at that level of detail, it should've worked. So the problem is somewhere in the details you left out ... Maybe you have a PATH that contains an older PG version in some other directory? regards, tom lane