From: Csaba Nagy <nagy@ecircle-ag.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Jim C. Nasby <jim@nasby.net>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Hints proposal
Date: Thu, 12 Oct 2006 19:15:40 +0200
Message-ID: <1160673340.28751.83.camel@coppola.muc.ecircle.de> (raw)
In-Reply-To: <1160671375.31966.84.camel@dogma.v10.wvs>
References: <20061012151439.GT28647@nasby.net>
<1160671375.31966.84.camel@dogma.v10.wvs>
> I'm not suggesting that we do that, but it seems better then embedding
> the hints in the queries themselves.
OK, what about this: if I execute the same query from a web client, I
want the not-so-optimal-but-safe plan, if I execute it asynchronously, I
let the planner choose the
best-overall-performance-but-sometimes-may-be-slow plan ?
What kind of statistics/table level hinting will get you this ?
I would say only query level hinting will buy you query level control.
And that's perfectly good in some situations.
I really can't see why a query-level hinting mechanism is so evil, why
it couldn't be kept forever, and augmented with the possibility of
correlation hinting, or table level hinting.
These are really solving different problems, with some overlapping...
Cheers,
Csaba.
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: nagy@ecircle-ag.com, pgsql@j-davis.com, jim@nasby.net
Subject: Re: Hints proposal
In-Reply-To: <1160673340.28751.83.camel@coppola.muc.ecircle.de>
* 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