From: | Guido Neitzer <guido(dot)neitzer(at)pharmaline(dot)de> |
---|---|
To: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgsql vs mysql |
Date: | 2006-07-11 18:01:32 |
Message-ID: | C8B64EF1-022B-43CE-AF66-5C6F33907D8B@pharmaline.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2006-07-11 18:06:59 | Re: SQL parsing suggestions? |
Previous Message | John DeSoi | 2006-07-11 17:54:38 | Re: SQL parsing suggestions? |