Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4B6149FA501 for ; Fri, 5 Jan 2007 14:02:20 -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 82671-10 for ; Fri, 5 Jan 2007 14:02:07 -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 4ABAA9FA182 for ; Fri, 5 Jan 2007 14:02:08 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by myemma.com (Postfix) with ESMTP id 41C5323CD8; Fri, 5 Jan 2007 12:02:07 -0600 (CST) Received: from myemma.com ([127.0.0.1]) by localhost (velma [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15216-02; Fri, 5 Jan 2007 12:02:05 -0600 (CST) Received: from [10.0.23.39] (unknown [209.149.59.218]) by myemma.com (Postfix) with ESMTP id 963E723CD2; Fri, 5 Jan 2007 12:02:05 -0600 (CST) Message-ID: <459E929C.9000607@myemma.com> Date: Fri, 05 Jan 2007 12:02:04 -0600 From: Erik Jones User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Erik Jones Cc: Tom Lane , 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> <459BFD1C.80707@myemma.com> In-Reply-To: <459BFD1C.80707@myemma.com> 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/70 X-Sequence-Number: 22671 Erik Jones wrote: > 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! > Ok, this ended up taking a bit longer to get to due to the fact that we've been building indexes on our user tables off and on for the last few days. But, I'm back on it now. Here is my general plan of action: I'm going to do a schema dump of the pg_catalog schema from a fresh, clean 8.2 install and, tomorrow night after I do the same against the db we've been having issues with, diff the two to see if there are any glaring discrepancies. While running the dump from the live db I will have statement logging on for the dump, are there any queries or query lengths that I should pay particular attention to? -- erik jones software development emma(r)