Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 01BF4476279 for ; Tue, 14 Jan 2003 10:59:18 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id C019347709D for ; Tue, 14 Jan 2003 10:51:52 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0EFps5u016125; Tue, 14 Jan 2003 10:51:55 -0500 (EST) To: "mdc@keko.com.ar" Cc: "pgsql-sql@postgresql.org" Subject: Re: database broken ? In-reply-to: <3e242278.ec7.16838@keko.com.ar> References: <3e242278.ec7.16838@keko.com.ar> Comments: In-reply-to "mdc@keko.com.ar" message dated "Tue, 14 Jan 2003 11:45:12 -0300" Date: Tue, 14 Jan 2003 10:51:53 -0500 Message-ID: <16124.1042559513@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/202 X-Sequence-Number: 11067 "mdc@keko.com.ar" writes: > Database version: PostgreSQL 7.2.3 on i686-pc-linux-gnu, > compiled by GCC 2.96 > Archiver (db) version:7.1.2 > Proceeding deespite mistmatch. > What's going wrong? It told you: you're using the wrong pg_dump. Apparently you have overridden that error check rather than finding where you put the right pg_dump. regards, tom lane