| From: | Guido Neitzer <guido(dot)neitzer(at)pharmaline(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pgsql vs mysql |
| Date: | 2006-07-11 20:20:56 |
| Message-ID: | 328A4B5D-D1D7-4B9D-A5AE-D766C9D6103A@pharmaline.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11.07.2006, at 21:11 Uhr, Alvaro Herrera wrote:
>> I had the problem a few months ago, where my app server plugin and
>> the jdbc driver used prepared statements for selecting stuff from the
>> database. Most of the time, indexes weren't used at all, so
>> PostgreSQL performance was the worst I've ever seen in this
>> environment.
>
> I'm pretty excited about this idea of yours on how to fix this
> problem.
> Does it involve the histogram at all?
There is no idea. It's only not using prepared statements right now.
You can force this in the jdbc driver (using protocolVersion=2 in the
connection url) or you can send different stuff from the application.
There is nothing where the DB itself does anything.
Nothing special.
cug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2006-07-11 20:24:37 | Re: pgsql vs mysql |
| Previous Message | Bruce Momjian | 2006-07-11 20:18:55 | Re: doesn't recognize "!=-" (not equal to a negative |