X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 358CC3A40B1 for ; Mon, 8 Nov 2004 21:36:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 41930-01 for ; Mon, 8 Nov 2004 21:36:53 +0000 (GMT) Received: from ws6-3.us4.outblaze.com (ws6-3.us4.outblaze.com [205.158.62.199]) by svr1.postgresql.org (Postfix) with SMTP id EF63C3A40A7 for ; Mon, 8 Nov 2004 21:36:54 +0000 (GMT) Received: (qmail 4323 invoked from network); 8 Nov 2004 21:36:53 -0000 Received: from unknown (HELO ?192.168.0.204?) (michael@hipp.com@69.152.47.198) by ws6-3.us4.outblaze.com with SMTP; 8 Nov 2004 21:36:53 -0000 Message-ID: <418FE72F.6050601@Hipp.com> Date: Mon, 08 Nov 2004 15:37:51 -0600 From: Michael Hipp User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: pgsql-admin@postgresql.org Subject: Re: psql won't accept pg_dump References: <418FC8DD.5080102@Hipp.com> <9977.1099944672@sss.pgh.pa.us> In-Reply-To: <9977.1099944672@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/64 X-Sequence-Number: 15449 Tom Lane wrote: > Michael Hipp writes: > >>######### CASE #1 >>psql:test.psql:18: ERROR: unrecognized configuration parameter >>"default_with_oids" > > Apparently you're trying to use an 8.0 pg_dump with a 7.4 backend. > > >>######### CASE #2 >>psql:test.psql:42: ERROR: invalid input syntax for type timestamp: >>"2004-10-30 >>21:11:00 501 so3 Test Sat morning CMH 2004-10-30 11:11:43.25 >>michael unknown" >>CONTEXT: COPY dailylog, line 1, column enttime: "2004-10-30 21:11:00 >>501 so3 >> Test Sat morning CMH 2004-10-30 11:11:43.25 michael unknown" > > This looks to me like something has changed the tab separators between > columns into spaces. > > regards, tom lane You were right on both counts. Thank you! Michael