Re: pgsql vs mysql - Mailing list pgsql-general

From Guido Neitzer
Subject Re: pgsql vs mysql
Date
Msg-id C8B64EF1-022B-43CE-AF66-5C6F33907D8B@pharmaline.de
Whole thread Raw
In response to Re: pgsql vs mysql  ("Merlin Moncure" <mmoncure@gmail.com>)
Responses Re: pgsql vs mysql  ("Merlin Moncure" <mmoncure@gmail.com>)
Re: pgsql vs mysql  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
On 11.07.2006, at 19:36 Uhr, Merlin Moncure wrote:

> As to preparing
> statements, I agree in principle although I don't know if that is a
> good argument not to make the non-paramaterized interface more
> powerful.

It is not, as prepared statements have the problem that they are only
optimized once and very generically and without actual knowledge of
the parameter content, this is just useless.

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.

There are fixes for that, but it should be made easier ...

cug

pgsql-general by date:

Previous
From: John DeSoi
Date:
Subject: Re: SQL parsing suggestions?
Next
From: "Ed L."
Date:
Subject: troubleshooting 8.1.2