From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Hinting the planner |
Date: | 2008-01-02 17:19:52 |
Message-ID: | 60r6h0du13.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
mgainty(at)hotmail(dot)com (Martin Gainty) writes:
> Not the planner but you can hint the query as in this example
> select /*+ ordered use_hash(code1)*/ * from table_1;
That might have some effect with Oracle; is there some reason why you
think this would be expected to have any effect on a PostgreSQL query?
--
select 'cbbrowne' || '@' || 'acm.org';
http://www3.sympatico.ca/cbbrowne/x.html
Rules of the Evil Overlord #178. "If I have the hero cornered and am
about to finish him off and he says "Look out behind you!!" I will not
laugh and say "You don't expect me to fall for that old trick, do
you?" Instead I will take a step to the side and half turn. That way I
can still keep my weapon trained on the hero, I can scan the area
behind me, and if anything was heading for me it will now be heading
for him." <http://www.eviloverlord.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-02 18:00:32 | Re: visibility rules for AFTER UPDATE Constraint Triggers Function |
Previous Message | Jan Sunavec | 2008-01-02 17:03:48 | tsearch2 headline options |