From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Talking about optimizer, my long dream |
Date: | 2011-02-05 05:38:07 |
Message-ID: | 4D4CE23F.4070500@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
O
> If Oracle can patch their query planner for you in 24 hours, and you
> can apply patch with confidence against your test then production
> servers in an hour or so, great. Til then I'll stick to a database
> that has the absolutely, without a doubt, best coder support of any
> project I've ever used.
>
> My point in the other thread is that if you can identify a point where
> a hint would help, like my situation above, you're often better off
> presenting a test case here and getting a patch to make it smarter.
>
By way of contrast - I had a similar situation with DB2 (a few years
ago) with a bad plan being chosen for BETWEEN predicates in some cases.
I found myself having to spend about a hour or two a week chasing the
support organization for - wait for it - 6 months to get a planner patch!
From | Date | Subject | |
---|---|---|---|
Next Message | david | 2011-02-05 05:46:30 | Re: [HACKERS] Slow count(*) again... |
Previous Message | Greg Smith | 2011-02-05 05:03:08 | Re: table partitioning and select max(id) |