Re: Hints WAS: Index Tuning Features - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Hints WAS: Index Tuning Features
Date
Msg-id 452E6C82.7020405@agliodbs.com
Whole thread Raw
In response to Re: Hints WAS: Index Tuning Features  ("Mark Woodward" <pgsql@mohawksoft.com>)
Responses Re: Hints WAS: Index Tuning Features  ("Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
Mark,

> That is sort of the stopping block. None of us "know" what it should look
> like, but leaving the topic as "if you want it, go do the work and submit
> a patch." Isn't going to get it done.
> 
> First we should decide if it is, in fact, something that ought to happen,
> then if that happens, we should think about what it should be.

Well, that's what the *rest* of us are doing on the two threads ... 
here, and "Simple Join Optimized Badly" on performance.  You're the only 
one who seems to want others to do the specification work for him. 
Start making suggestions, and stop criticizing the process.

And, to give you a starting point: the discussion has morphed into: 
"What manual ways can we come up with for the DBA to influence the 
planner and fix planner "bugs" which won't have the fragility of 
query-based hints ala Oracle?"


--Josh Berkus




pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: [PERFORM] Hints proposal
Next
From: Tom Lane
Date:
Subject: Re: Getting the type Oid in a CREATE TYPE output function ..