From: Alvaro Herrera <alvherre@commandprompt.com>
To: David Kerr <dmk@mr-paradox.net>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: PARSE WAITING
Date: Mon, 23 Aug 2010 18:23:25 -0400
Message-ID: <1282602153-sup-6272@alvh.no-ip.org> (raw)
In-Reply-To: <20100823221556.GC79389@mr-paradox.net>
References: <20100823221556.GC79389@mr-paradox.net>
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 <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alvherre@commandprompt.com, dmk@mr-paradox.net
Subject: Re: PARSE WAITING
In-Reply-To: <1282602153-sup-6272@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox