| From: | Dimitri <dimitrik(dot)fr(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Chris <dmagick(at)gmail(dot)com>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Any better plan for this query?.. |
| Date: | 2009-05-06 14:31:35 |
| Message-ID: | 5482c80a0905060731h7d561ef0nc68cf782f8125815@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
I supposed in case with prepare and then execute a query optimizer is
no more coming in play on "execute" phase, or did I miss something?..
Forget to say: query cache is disabled on MySQL side.
Rgds,
-Dimitri
On 5/6/09, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> wrote:
> Dimitri wrote:
>> Hi Chris,
>>
>> the only problem I see here is it's 2 times slower vs InnoDB, so
>> before I'll say myself it's ok I want to be sure there is nothing else
>> to do.. :-)
>
> Can the genetic query optimizer come into play on small queries?
>
> --
> Craig Ringer
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Marshall | 2009-05-06 14:34:46 | Re: Any better plan for this query?.. |
| Previous Message | Matthew Wakeling | 2009-05-06 14:28:46 | Re: Any better plan for this query?.. |