Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4E9A59F9F8F for ; Wed, 3 Jan 2007 14:59:57 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 11794-03 for ; Wed, 3 Jan 2007 14:59:36 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from myemma.com (db1.e2ma.net [66.179.147.163]) by postgresql.org (Postfix) with ESMTP id ECD169FA0EE for ; Wed, 3 Jan 2007 14:59:43 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by myemma.com (Postfix) with ESMTP id 021A023D05; Wed, 3 Jan 2007 12:59:43 -0600 (CST) Received: from myemma.com ([127.0.0.1]) by localhost (velma [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11062-03; Wed, 3 Jan 2007 12:59:42 -0600 (CST) Received: from [10.0.23.39] (unknown [209.149.59.218]) by myemma.com (Postfix) with ESMTP id 5BAFD23CE7; Wed, 3 Jan 2007 12:59:42 -0600 (CST) Message-ID: <459BFD1C.80707@myemma.com> Date: Wed, 03 Jan 2007 12:59:40 -0600 From: Erik Jones User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Tom Lane Cc: Guillaume Smet , pgsql-performance@postgresql.org Subject: Re: More 8.2 client issues (Was: [Slow dump?) References: <459AD5A8.7030102@myemma.com> <22512.1167779361@sss.pgh.pa.us> <459BD61C.3030202@myemma.com> <11617.1167841479@sss.pgh.pa.us> <459BDC98.8030008@myemma.com> <1d4e0c10701030850h78f19e74hfa7c25c01ded9a61@mail.gmail.com> <459BE4BB.4070601@myemma.com> <13359.1167844898@sss.pgh.pa.us> <459BEEB8.5050405@myemma.com> <16137.1167848799@sss.pgh.pa.us> In-Reply-To: <16137.1167848799@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at myemma.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/44 X-Sequence-Number: 22645 Tom Lane wrote: > Erik Jones writes: > >> That's a good idea, but first I'll still need to run it by my sysadmin >> wrt space -- our dump files are around 22GB when we can let them finish >> these days. >> > > Given that we're now speculating about regex problems, you could do a > test run of "pg_dump -s" with logging enabled; that shouldn't take an > unreasonable amount of time or space. > > regards, tom lane > Sounds like a post-lunch plan! By the way, even though this isn't even solved yet, thank you for all of your help! -- erik jones software development emma(r)