pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jaime Casanova <systemguards@gmail.com>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Mark Kirkwood <markir@paradise.net.nz>
Cc: Craig A. James <cjames@modgraph-usa.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Overriding the optimizer
Date: Sat, 17 Dec 2005 07:31:40 -0500
Message-ID: <c2d9e70e0512170431m1275018cq363851364cdbb54b@mail.gmail.com> (raw)
In-Reply-To: <20051216224512.GX53809@pervasive.com>
References: <200512141603.52583.blargity@gmail.com>
	<1134629567.14248.27.camel@firebolt>
	<200512150148.16125.blargity@gmail.com>
	<1134644526.14248.60.camel@firebolt>
	<43A1C40D.8040006@paradise.net.nz>
	<43A1F6DB.3080805@modgraph-usa.com>
	<43A226E7.7040508@paradise.net.nz>
	<43A22BE3.6020103@modgraph-usa.com>
	<43A231AA.9070708@paradise.net.nz>
	<20051216224512.GX53809@pervasive.com>

> > Yeah it would - an implementation I have seen that I like is where the
> > developer can supply the *entire* execution plan with a query. This is
> > complex enough to make casual use unlikely :-), but provides the ability
> > to try out other plans, and also fix that vital query that must run
> > today.....
>
> Being able to specify an exact plan would also provide for query plan
> stability; something that is critically important in certain
> applications. If you have to meet a specific response time requirement
> for a query, you can't afford to have the optimizer suddenly decide that
> some other plan might be faster when in fact it's much slower.

Plan stability doesn't mean time response stability...
The plan that today is almost instantaneous tomorrow can take hours...

--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)



view thread (41+ messages)  latest in thread

Message-ID: <c2d9e70e0512170431m1275018cq363851364cdbb54b@mail.gmail.com>
Permalink:  ../c2d9e70e0512170431m1275018cq363851364cdbb54b@mail.gmail.com/
Also on:    postgresql.org/message-id/c2d9e70e0512170431m1275018cq363851364cdbb54b@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: systemguards@gmail.com, jnasby@pervasive.com, markir@paradise.net.nz, cjames@modgraph-usa.com
  Subject: Re: Overriding the optimizer
  In-Reply-To: <c2d9e70e0512170431m1275018cq363851364cdbb54b@mail.gmail.com>
  References: <200512141603.52583.blargity@gmail.com> <1134629567.14248.27.camel@firebolt> <200512150148.16125.blargity@gmail.com> <1134644526.14248.60.camel@firebolt> <43A1C40D.8040006@paradise.net.nz> <43A1F6DB.3080805@modgraph-usa.com> <43A226E7.7040508@paradise.net.nz> <43A22BE3.6020103@modgraph-usa.com> <43A231AA.9070708@paradise.net.nz> <20051216224512.GX53809@pervasive.com> <c2d9e70e0512170431m1275018cq363851364cdbb54b@mail.gmail.com>

* 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