From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | alvherre(at)commandprompt(dot)com |
Cc: | "Guido Neitzer" <guido(dot)neitzer(at)pharmaline(dot)de>, "PostgreSQL General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgsql vs mysql |
Date: | 2006-07-12 13:15:38 |
Message-ID: | b42b73150607120615x12e54c0fl148c4fd508f578c0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/11/06, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Guido Neitzer wrote:
> > On 11.07.2006, at 19:36 Uhr, Merlin Moncure wrote:
> > 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.
>
> I'm pretty excited about this idea of yours on how to fix this problem.
> Does it involve the histogram at all?
I've thought for a long time the best way to handle this problem is to
allow supplying a hint for any parameter. For example, I like to
paramterize the limit statement whicih is actually pretty neat but the
planner (iirc) assumes 10% and so resorts to seqscan/bitmapscan in
these cases.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Juan Ignacio Lalla | 2006-07-12 13:23:53 | Crystal Reports 8.5 - SQL Expressions |
Previous Message | Carl M. Nasal II | 2006-07-12 12:32:57 | Re: PostgreSQL Server Crash using plPHP or PL/Perl |