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

From Zeugswetter Andreas SB
Subject AW: AW: AW: AW: [HACKERS] Some notes on optimizer cost estimates
Date
Msg-id 219F68D65015D011A8E000006F8590C603FDC228@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List pgsql-hackers
> >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? :)

SELECT {+ INDEX (a auftragsbeleg_index2)} a.id_beleg       FROM auftragsbeleg a, instparameter i WHERE
a.num_mandant=i.num_mandantAND cod_prioritaets=?       AND num_prior_eingang<? 
 
SELECT {+ ORDERED } * from tab1, tab2, tab3 .....

SELECT {+ FULL (tab1) } * from tab1, tab2, ....
SELECT {+ AVOID_FULL (tab1) } * from tab1, tab2, ....

Informix places the directives in comments, so that the resulting sql
does not violate SQL92.
The directive is identified by the {+

Andreas


pgsql-hackers by date:

Previous
From: Patrick Welche
Date:
Subject: Re: [HACKERS] (libpq) Anyone still having problems with COPY?
Next
From: Hannu Krosing
Date:
Subject: Re: OIDS (Re: [HACKERS] Well, then you keep your darn columns)