Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id C9DCD9FA18F for ; Wed, 3 Jan 2007 12:41:05 -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 28728-05 for ; Wed, 3 Jan 2007 12:40:59 -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 A14929F931E for ; Wed, 3 Jan 2007 12:40:59 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by myemma.com (Postfix) with ESMTP id 3114923CFA; Wed, 3 Jan 2007 10:40:59 -0600 (CST) Received: from myemma.com ([127.0.0.1]) by localhost (velma [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19139-02; Wed, 3 Jan 2007 10:40:58 -0600 (CST) Received: from [10.0.23.39] (unknown [209.149.59.218]) by myemma.com (Postfix) with ESMTP id 82E9623CCE; Wed, 3 Jan 2007 10:40:58 -0600 (CST) Message-ID: <459BDC98.8030008@myemma.com> Date: Wed, 03 Jan 2007 10:40:56 -0600 From: Erik Jones User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Tom Lane Cc: 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> In-Reply-To: <11617.1167841479@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/35 X-Sequence-Number: 22636 Tom Lane wrote: > Erik Jones writes: > >> ... >> sigaction(SIGPIPE, 0x08046E20, 0x08046E70) = 0 >> send(4, " Q\0\0\0E5 S E L E C T ".., 230, 0) = 230 >> <----------------------------------------------------------- Hang is >> right here! >> sigaction(SIGPIPE, 0x08046E20, 0x08046E70) = 0 >> pollsys(0x08046EE8, 1, 0x00000000, 0x00000000) (sleeping...) >> pollsys(0x08046EE8, 1, 0x00000000, 0x00000000) = 1 >> recv(4, " T\0\0\0 P\003 o i d\0\0".., 16384, 0) = 140 >> ... >> > > Hmph. So it seems the delay really is on the server's end. Any chance > you could truss the connected backend process too and see what it's doing? > > Actually ... before you do that, the first query for "\d pg_class" > should look like > > SELECT c.oid, > n.nspname, > c.relname > FROM pg_catalog.pg_class c > LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace > WHERE c.relname ~ '^(pg_class)$' > AND pg_catalog.pg_table_is_visible(c.oid) > ORDER BY 2, 3; > > I could see this taking an unreasonable amount of time if you had a huge > number of pg_class rows or a very long search_path --- is your database > at all out of the ordinary in those ways? > Well, running "select count(*) from pg_class;" returns 524699 rows and our search path is the default. I'd also like to reiterate that \d pg_class returns instantly when run from the 8.1.4 psql client connected to the 8.2 db. How would I go about determining which backend server process psql was attached to? -- erik jones software development emma(r)