Re: Trying to track down weird query stalls

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: dan(at)sidhe(dot)org
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Trying to track down weird query stalls
Date: 2009-03-30 21:38:39
Message-ID: 20090330213839.GJ23023@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

dan(at)sidhe(dot)org escribió:

> Fair enough. (And sorry about the mis-read) Next time this occurs I'll try
> and duplicate this in psql. FWIW, a quick read of the C underlying the
> DBD::Pg module shows it using PQexecPrepared, so I'm pretty sure it is
> using prepared statements with placeholders, but double-checking seems
> prudent.

Yes, but I doubt that it'll be smart enough to work for EXPLAIN in the
way we need here.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Carey 2009-03-30 21:44:50 Re: Trying to track down weird query stalls
Previous Message dan 2009-03-30 21:34:17 Re: Trying to track down weird query stalls