Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 02E8B9FA304 for ; Tue, 2 Jan 2007 02:02:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 15713-03 for ; Tue, 2 Jan 2007 02:02:37 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from 66-226-76-106.dedicated.abac.net (66-226-76-106.dedicated.abac.net [66.226.76.106]) by postgresql.org (Postfix) with ESMTP id 854679FA31B for ; Tue, 2 Jan 2007 02:02:37 -0400 (AST) Received: (qmail 27691 invoked by uid 2020); 1 Jan 2007 23:08:43 -0800 Received: from wsip-70-167-125-69.sd.sd.cox.net (HELO ?192.168.0.3?) (70.167.125.69) by 192.168.0.4 with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jan 2007 23:08:43 -0800 Message-ID: <4599F5A6.1070102@modgraph-usa.com> Date: Mon, 01 Jan 2007 22:03:18 -0800 From: "Craig A. James" User-Agent: Thunderbird 1.5.0.9 (X11/20061206) MIME-Version: 1.0 To: Tom Lane CC: pgsql-performance@postgresql.org Subject: Re: glibc double-free error References: <4599B57A.3080207@modgraph-usa.com> <22106.1167701992@sss.pgh.pa.us> In-Reply-To: <22106.1167701992@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.908 tagged_above=0 required=5 tests=AWL, BAYES_50, HELO_DYNAMIC_IPADDR2 X-Spam-Level: ** X-Archive-Number: 200701/7 X-Sequence-Number: 22608 Tom Lane wrote: > "Craig A. James" writes: >> I'm using pg_dump/pg_restore to quickly copy databases between servers. But my server keeps crashing when I run pg_restore: >> glibc detected *** double free or corruption (!prev): 0x0a00b1a0 > >> What can I do to help diagnose this problem? > > Either dig into it yourself with gdb, or send me a not-too-large example > dump file (off-list)... Hmmm ... after moving to our production server, four hours of work copying a dozen databases, there hasn't been a single glibc problem. The development server is Fedora Core 3, the productions server is Fedora Core 4. Unless it happens on FC4, I'm diagnosing that it's a glibc bug or incompatibility that was already fixed. Thanks, Craig