| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Don Baccus <dhogaza(at)pacifier(dot)com>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: AW: AW: AW: [HACKERS] Some notes on optimizer cost estimates |
| Date: | 2000-01-27 09:39:57 |
| Message-ID: | 3890126D.555964F9@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-01-27 09:55:10 | AW: AW: AW: AW: [HACKERS] Some notes on optimizer cost estimates |
| Previous Message | Tom Lane | 2000-01-27 07:42:26 | Re: [HACKERS] CVS problem |