pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Andy Lester <andy@petdance.com>
Cc: Craig Ringer <ringerc@ringerc.id.au>
Cc: Royce Ausburn <royce.ml@inomial.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Prepared statements and suboptimal plans
Date: Tue, 20 Sep 2011 23:43:38 -0400
Message-ID: <13063.1316576618@sss.pgh.pa.us> (raw)
In-Reply-To: <20110921023830.GW12765@tamriel.snowman.net>
References: <C38A9B65-3AEB-4AFC-AE49-8D61B2DEDF64@inomial.com>
	<4E792417.5080205@ringerc.id.au>
	<9289.1316565395@sss.pgh.pa.us>
	<7B0A863F-F304-4057-807B-9B2E6137E107@petdance.com>
	<10687.1316566832@sss.pgh.pa.us>
	<20110921023830.GW12765@tamriel.snowman.net>

Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> really pretty simple: decide whether to use a custom (parameter-aware)
>> plan or a generic (not-parameter-aware) plan.  

> Before I go digging into this, I was wondering, is this going to address
> our current problem of not being able to use prepared queries and
> constraint exclusion..?

Possibly ... you didn't say exactly what your problem consists of.

			regards, tom lane



view thread (13+ messages)  latest in thread

Message-ID: <13063.1316576618@sss.pgh.pa.us>
Permalink:  ../13063.1316576618@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13063.1316576618@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, sfrost@snowman.net, andy@petdance.com, ringerc@ringerc.id.au, royce.ml@inomial.com
  Subject: Re: Prepared statements and suboptimal plans
  In-Reply-To: <13063.1316576618@sss.pgh.pa.us>

* 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