| From: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Andrew Sullivan" <ajs(at)crankycanuck(dot)ca>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PERFORM] Hints proposal |
| Date: | 2006-10-13 08:41:36 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA579016A0981@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
> The _other_ way it's going to be used is as a stealthy
> alteration to regular behaviour, to solve a particular nasty
> performance problem that happens to result on a given day.
> And every single time I've seen anything like that done, the
> long term effect is always monstrous.
Funny, I very seldom use Informix hints (mostly none, maybe 2 per
project),
but I have yet to see one that backfires on me, even lightly.
I use hints like: don't use that index, use that join order, use that
index
Can you give us an example that had such a monstrous effect in Oracle,
other than that the hint was a mistake in the first place ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas ADI SD | 2006-10-13 09:07:29 | Re: [HACKERS] Hints proposal |
| Previous Message | Martijn van Oosterhout | 2006-10-13 08:12:18 | Re: ./configure argument checking |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas ADI SD | 2006-10-13 09:07:29 | Re: [HACKERS] Hints proposal |
| Previous Message | Christopher Browne | 2006-10-13 03:12:29 | Re: [PERFORM] Hints proposal |