Re: Any better plan for this query?..

From: Andres Freund <andres(at)anarazel(dot)de>
To: Dimitri <dimitrik(dot)fr(at)gmail(dot)com>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Any better plan for this query?..
Date: 2009-05-12 07:43:13
Message-ID: 4A092891.90100@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi,

On 05/12/2009 12:46 AM, Dimitri wrote:
> So, why I don't use prepare here: let's say I'm testing the worst
> stress case :-) Imagine you have thousands of such kind of queries -
> you cannot prepare all of them! :-) or you'll maybe prepare it once,
> but as I showed previously in this thread prepare statement itself
> takes 16ms, so for a single shot there is no gain! :-)
I have a hard time imaging a high throughput OLTP workload with that
many different queries ;-)

Naturally it would still be nice to be good in this not optimal workload...

Andres

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dimitri Fontaine 2009-05-12 08:44:09 Re: Any better plan for this query?..
Previous Message Dimitri 2009-05-12 07:36:31 Re: Any better plan for this query?..