From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Bucky Jordan" <bjordan(at)lumeta(dot)com>, Rohit_Behl <Rohit_Behl(at)infosys(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Jdbc/postgres performance |
Date: | 2006-10-18 13:31:41 |
Message-ID: | b42b73150610180631v6b8e1796v43855baa8087979c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 10/18/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
> > this is not really a jdbc issue, just a practical problem with
> > prepared statements...
>
> Specifically, that the OP is running a 7.4 backend, which was our
> first venture into prepared parameterized statements. PG 8.1 will
> do better, 8.2 should do better yet.
I haven't looked at 8.2 because I no longer work at my previous
position, but I was significantly affected by this problem through the
8.1 release. The speed advantages of preparing certain types queries
are dramatic and there are some decent use cases for pramaterizing
limit and other input parameters that are difficult to guess.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2006-10-18 13:57:25 | Re: Index on two columns not used |
Previous Message | Merlin Moncure | 2006-10-18 13:20:54 | Re: Jdbc/postgres performance |