Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e5S6Fr159341 for ; Wed, 28 Jun 2000 02:15:53 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id CAA14459; Wed, 28 Jun 2000 02:15:40 -0400 (EDT) To: Ryan Bradetich cc: pgsql-sql@postgresql.org Subject: Re: Problem with pg_dumpall In-reply-to: <3959355B.762D586C@hp.com> References: <3958D5EA.82E74C68@hp.com> <14979.962142613@sss.pgh.pa.us> <395922BA.2F477593@hp.com> <16833.962143321@sss.pgh.pa.us> <3959355B.762D586C@hp.com> Comments: In-reply-to Ryan Bradetich message dated "Tue, 27 Jun 2000 17:14:35 -0600" Date: Wed, 28 Jun 2000 02:15:40 -0400 Message-ID: <14456.962172940@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/250 Ryan Bradetich writes: > That was the problem. Good job at spotting that Tom. I just successfully > completed a backup without using the -o > option to pg_dumpall. OK, if you need it with -o try the following patch against 7.0.2. regards, tom lane *** src/backend/commands/copy.c.orig Wed Jun 28 02:07:58 2000 --- src/backend/commands/copy.c Wed Jun 28 02:13:01 2000 *************** *** 484,491 **** if (oids && !binary) { ! CopySendString(oidout(tuple->t_data->t_oid), fp); CopySendChar(delim[0], fp); } for (i = 0; i < attr_count; i++) --- 484,493 ---- if (oids && !binary) { ! string = oidout(tuple->t_data->t_oid); ! CopySendString(string, fp); CopySendChar(delim[0], fp); + pfree(string); } for (i = 0; i < attr_count; i++)