From: Merlin Moncure <mmoncure@gmail.com>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] Hints proposal
Date: Thu, 12 Oct 2006 14:21:55 -0400
Message-ID: <b42b73150610121121o50c2b082l2b13d38fc3e00820@mail.gmail.com> (raw)
In-Reply-To: <20061012174503.GA29203@phlogiston.dyndns.org>
References: <20061012151439.GT28647@nasby.net>
<10866.1160667752@sss.pgh.pa.us>
<20061012162525.GF28647@nasby.net>
<20061012174503.GA29203@phlogiston.dyndns.org>
On 10/12/06, Andrew Sullivan <ajs@crankycanuck.ca> wrote:
> On Thu, Oct 12, 2006 at 11:25:25AM -0500, Jim C. Nasby wrote:
> > Yes, but it does one key thing: allows DBAs to fix problems *NOW*. See
> > also my comment below.
>
> If I may argue in the other direction, speaking as one whose career
> (if we may be generous enough to call it that) has been pretty much
> exclusively on the operations end of things, I think that's an awful
> idea.
>
> There are two ways that quick-fix solve-the-problem-now hints are
> going to be used. One is in the sort of one-off query that a DBA has
third way: to solve the problem of data (especially constants) not
being available to the planner at the time the plan was generated.
this happens most often with prepared statements and sql udfs. note
that changes to the plan generation mechanism (i think proposed by
peter e a few weeks back) might also solve this.
In a previous large project I had to keep bitmap scan and seqscan off
all the time because of this problem (the project used a lot of
prepared statements).
or am i way off base here?
merlin
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: mmoncure@gmail.com, ajs@crankycanuck.ca, pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] Hints proposal
In-Reply-To: <b42b73150610121121o50c2b082l2b13d38fc3e00820@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