Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 43A0A64FCCA for ; Wed, 17 Sep 2008 12:44:38 -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 86799-08 for ; Wed, 17 Sep 2008 12:44:34 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from web25801.mail.ukl.yahoo.com (web25801.mail.ukl.yahoo.com [217.12.10.186]) by postgresql.org (Postfix) with SMTP id 0C0A564FCC0 for ; Wed, 17 Sep 2008 12:44:33 -0300 (ADT) Received: (qmail 34489 invoked by uid 60001); 17 Sep 2008 15:44:29 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=2jS1ZDWMjv1R7YKH8sSRLkJEj15Uq5BBA3u4T7om9LVYIgWhxEP5p/I5RBSMP5a5Lie2yM47abD8w/FvndZbRzyESf0YdvmJ2BFoMwBwShnmAj64HoJZBBPgKTARhQy7ceF12iwbYwdhQMYp/HFNCyIJbwWus48VgFTucILg+sY=; X-YMail-OSG: b1DHvlUVM1nj1RwAAFQ1Z0LWDvdE1O_PO4xKMoVgY1La4YHGiXDd2SsUhylsEjjVJ1yCu43.HWsMOQL51obMvRNnG68ErPBIJcIBmckotYTw9_QwpWjwXpQu1qUwNpY0SY59FYBZt6.yNpMP0Sw6GWI6 Received: from [62.254.183.162] by web25801.mail.ukl.yahoo.com via HTTP; Wed, 17 Sep 2008 15:44:29 GMT X-Mailer: YahooMailWebService/0.7.218.2 Date: Wed, 17 Sep 2008 15:44:29 +0000 (GMT) From: Valentin Bogdanov Reply-To: valiouk@yahoo.co.uk Subject: Re: unable to backup database -- psql not up to date To: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <850986.33638.qm@web25801.mail.ukl.yahoo.com> 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/175 X-Sequence-Number: 30268 --- On Wed, 17/9/08, Jonathan Nalley wrote: > From: Jonathan Nalley > Subject: Re: [ADMIN] unable to backup database -- psql not up to date > To: "dbchristopher" , pgsql-admin@postgresql.org > Date: Wednesday, 17 September, 2008, 3:23 PM > On Tue, Sep 16, 2008 at 5:53 PM, dbchristopher > wrote: > > > > I upgraded to postgresql 8.3.3 a few weeks ago, and it > seems that while the > > server was upgraded, but for some reason none of the > accompanying software > > was (pg_dump, psql, etc) > > > > I get this error when I try to back up the database: > > pg_dump: server version: 8.3.3; pg_dump version: 8.2.6 > > pg_dump: aborting because of version mismatch (Use the > -i option to proceed > > anyway.) > > pg_dump: *** aborted because of error > > > > and likewise when I log into the psql client: > > WARNING: You are connected to a server with major > version 8.3, > > but your psql client is major version 8.2. Some > backslash commands, > > such as \d, might not work properly. > > > > How could this have happened? I really need to be able > to back up my > > information. I reinstalled the software and it > didn't change anything. What > > do I do to upgrade pg_dump to the newest version? >=20 > What OS are you running on? >=20 > How did you perform this upgrade? In a packaged form like > rpm? or > did you compile from source? yup, the postgres clients are usually shipped in their own packages, separa= te from the server package. I do have to manually upgrade the client packag= es on a Debian system. =0A=0A=0A