pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Theo Kramer <theo@flame.co.za>
To: pgsql-performance@postgresql.org
Subject: Re: Performance problems with prepared statements
Date: Fri, 12 Oct 2007 10:05:35 +0200
Message-ID: <1192176335.2470.20.camel@localhost.localdomain> (raw)
In-Reply-To: <slrnfgsqpi.27gg.andrew+nonews@atlantis.supernews.net>
References: <1192027540.2495.3.camel@localhost.localdomain>
	<470CE918.4060608@dalibo.com>
	<1192044840.2549.21.camel@fedmac>
	<slrnfgsqpi.27gg.andrew+nonews@atlantis.supernews.net>

On Thu, 2007-10-11 at 18:28 +0000, Andrew - Supernews wrote:
> On 2007-10-10, Theo Kramer <theo@flame.co.za> wrote:
> > When doing a 'manual' prepare and explain analyze I get the following
> >
> > rascal=# prepare cq (char(12), smallint, integer) as SELECT oid,
> > calllog_mainteng, calllog_phase, calllog_self FROM calllog
> > WHERE calllog_mainteng = $1
> > AND calllog_phase = $2
> > AND calllog_self < $3    
> > OR calllog_mainteng = $1            
> > AND calllog_phase < $2
> > ORDER BY calllog_mainteng DESC,
> >  calllog_phase DESC,
> >  calllog_self DESC limit 25;
> > PREPARE
> 
> When you do this from the application, are you passing it 3 parameters,
> or 5?  The plan is clearly taking advantage of the fact that the two
> occurrences of $1 and $2 are known to be the same value; if your app is
> using some interface that uses ? placeholders rather than numbered
> parameters, then the planner will not be able to make this assumption.

You may just have hit the nail on the head. I use numbered parameters
but have $1 to $5 ... let me take a look to see if I can change this.

> Also, from the application, is the LIMIT 25 passed as a constant or is that
> also a parameter?

A constant.

> 
-- 
Regards
Theo




view thread (18+ messages)  latest in thread

Message-ID: <1192176335.2470.20.camel@localhost.localdomain>
Permalink:  ../1192176335.2470.20.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1192176335.2470.20.camel@localhost.localdomain

 · 

reply

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: theo@flame.co.za
  Subject: Re: Performance problems with prepared statements
  In-Reply-To: <1192176335.2470.20.camel@localhost.localdomain>

* 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