Re: AW: AW: AW: [HACKERS] Some notes on optimizer cost estimates - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: AW: AW: AW: [HACKERS] Some notes on optimizer cost estimates
Date
Msg-id 3890126D.555964F9@tm.ee
Whole thread Raw
In response to Re: AW: AW: AW: [HACKERS] Some notes on optimizer cost estimates  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
Philip Warner wrote:
> 
> At 10:14 26/01/00 -0800, Don Baccus wrote:
> >At 01:25 PM 1/26/00 +0100, Zeugswetter Andreas SB wrote:
> >
> >>Yes, I think syntax to force or disallow a particular index,
> >>choose a join method or order, force/disallow seq scans ...
> >>is sometimes useful.
> >>Even Informix, who always refused to supply such a feature
> >>now has it.
> >
> >Can you give some sample syntax, for those of us who aren't
> >really database people but merely trying to maintain a facade? :)
> 
> There are two schemes I know if, one is the Microsoft (and I think Orcale)

IIRC Oracle hides the optimiser hints in comments, at least it does not 
directly sabotage portability.

I just remember reading an article about this in a magazine, have never used 
it myself.

-----------
Hannu


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: OIDS (Re: [HACKERS] Well, then you keep your darn columns)
Next
From: Michael Meskes
Date:
Subject: Re: [HACKERS] CVS problem