| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
| Cc: | Guillaume Cottenceau <gc(at)mnc(dot)ch>, Mario Splivalo <mario(dot)splivalo(at)megafon(dot)hr>, pgsql-performance(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: [PERFORM] Query much slower when run from postgres function |
| Date: | 2009-03-09 17:16:34 |
| Message-ID: | 5165.1236618994@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc pgsql-performance |
Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> writes:
> Unnamed prepared statements are planned after binding the values,
> starting with 8.3, or more precisely starting with 8.3.2 as early 8.3
> versions were partially broken on this behalf.
No, 8.2 did it too (otherwise we wouldn't have considered 8.3.0 to be
broken...). The thing I'm not too clear about is what "use of an
unnamed statement" translates to for a JDBC user.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Wenk | 2009-03-09 17:42:16 | Re: [PERFORM] Query much slower when run from postgres function |
| Previous Message | Guillaume Smet | 2009-03-09 17:04:23 | Re: [PERFORM] Query much slower when run from postgres function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Wenk | 2009-03-09 17:42:16 | Re: [PERFORM] Query much slower when run from postgres function |
| Previous Message | Guillaume Smet | 2009-03-09 17:04:23 | Re: [PERFORM] Query much slower when run from postgres function |