Skip site navigation (1) Skip section navigation (2)

Re: generalizing the planner knobs

From: "Pollard, Mike" <mpollard(at)cincom(dot)com>
To: <gsstark(at)mit(dot)edu>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>,"Neil Conway" <neilc(at)samurai(dot)com>,"pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: generalizing the planner knobs
Date: 2005-12-02 12:57:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Greg Stark gsstark(at)mit(dot)edu writes:
> You more or less missed my entire point.

Only because I am still getting used to how powerful and flexible
Postgres is; but I am working on expanding my horizons.

> In the extreme, no amount of added intelligence in the optimizer is
> to
> help it come up with any sane selectivity estimate for something like
>   WHERE radius_authenticate(user) = 'OK'

yeah, I can see where something like this would be problematic.  While I
still think that in an ideal world, you want to leave all of this to the
engine, it is true that in the real world sometimes we still have to do
some of the thinking for the computer.  It's just that I've seen code
absolutely littered with optimizer hints, and that really bothers me.
But you can't not build a useful tool just because some would abuse it.

Mike Pollard
SUPRA Server SQL Engineering and Support
Cincom Systems, Inc.

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-12-02 14:14:31
Subject: Re: [HACKERS] Should libedit be preferred to libreadline?
Previous:From: Michael GlaesemannDate: 2005-12-02 11:56:26
Subject: Re: Buildfarm: Bear, Branch 2?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group