| From: | Yang Zhang <yanghatespam(at)gmail(dot)com> |
|---|---|
| To: | Maciek Sakrejda <msakrejda(at)truviso(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Any way to *not* use server-side prepared statements in Postgresql? |
| Date: | 2011-07-19 02:49:27 |
| Message-ID: | CAKxBDU-AG-RTWWenN53xp0M88yx9oi0mBSdbaKMcJYDCSLjPRw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
They're slower (by about 4x on our boxes) for cases where statements
are being generated beyond simple value parameters, such as trying
many distinct projections.
On Mon, Jul 18, 2011 at 7:47 PM, Maciek Sakrejda <msakrejda(at)truviso(dot)com> wrote:
> It doesn't look like it. Any particular use case for this? The driver
> uses unnamed prepared statements here, and I'd be curious to hear
> where they are slower.
> ---
> Maciek Sakrejda | System Architect | Truviso
>
> 1065 E. Hillsdale Blvd., Suite 215
> Foster City, CA 94404
> (650) 242-3500 Main
> www.truviso.com
>
--
Yang Zhang
http://yz.mit.edu/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2011-07-19 02:50:46 | Re: Any way to *not* use server-side prepared statements in Postgresql? |
| Previous Message | Maciek Sakrejda | 2011-07-19 02:47:52 | Re: Any way to *not* use server-side prepared statements in Postgresql? |