| From: | James Mansion <james(at)mansionfamily(dot)plus(dot)com> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, 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 20:35:14 |
| Message-ID: | 49B57D82.4030706@mansionfamily.plus.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc pgsql-performance |
>
> The driver will use unnamed statements for all statements until it
> sees the same statement N times where N is 5 I believe, after that it
> uses a named statement.
>
>
Shame there's no syntax for it to pass the a table of the parameters to
the server when it creates the named statement as planner hints.
James
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Carey | 2009-03-09 20:56:01 | Re: [PERFORM] Query much slower when run from postgres function |
| Previous Message | Dave Cramer | 2009-03-09 19:56:53 | Re: [PERFORM] Query much slower when run from postgres function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Carey | 2009-03-09 20:56:01 | Re: [PERFORM] Query much slower when run from postgres function |
| Previous Message | Dave Cramer | 2009-03-09 19:56:53 | Re: [PERFORM] Query much slower when run from postgres function |