Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 38BF663292A for ; Mon, 23 Aug 2010 19:24:00 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 48479-02 for ; Mon, 23 Aug 2010 22:23:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (unknown [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 4EAFD632919 for ; Mon, 23 Aug 2010 19:23:52 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id C01E4348034; Mon, 23 Aug 2010 15:23:30 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dCCVPH2qnk31; Mon, 23 Aug 2010 15:23:28 -0700 (PDT) Received: from perhan.alvh.no-ip.org (200-85-200-241.bk3-dsl.surnet.cl [200.85.200.241]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id 2B026348002; Mon, 23 Aug 2010 15:23:28 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id BF06F6E510; Mon, 23 Aug 2010 18:23:25 -0400 (CLT) Content-Type: text/plain; charset=UTF-8 Cc: pgsql-performance Subject: Re: PARSE WAITING From: Alvaro Herrera To: David Kerr In-reply-to: <20100823221556.GC79389@mr-paradox.net> References: <20100823221556.GC79389@mr-paradox.net> Date: Mon, 23 Aug 2010 18:23:25 -0400 Message-Id: <1282602153-sup-6272@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.107 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RDNS_NONE=0.793 X-Spam-Level: X-Archive-Number: 201008/271 X-Sequence-Number: 40114 Excerpts from David Kerr's message of lun ago 23 18:15:56 -0400 2010: > Howdy all, > > We're doing some performance testing, and when we scaled it our app up to about 250 concurrent users > we started seeing a bunch of processes sititng in "PARSE WAITING" state. > > Can anyone give me insite on what this means? what's the parse waiting for? It means the parse phase is waiting for a lock. You can see exactly what it's waiting for by looking at pg_locks "WHERE NOT GRANTED". Have you got lots of partitions, or something? -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support