| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> |
| Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: setPrepareThreshold |
| Date: | 2014-01-17 15:47:41 |
| Message-ID: | CADK3HHKRUxRO9_Lf_FKAmdf3jEW=DNLM1_jRL-n26LS6TjZE7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
It defaults to 5. Basically if you reuse a prepared statement 5 times it
will convert it from an unnamed portal to a named statement. Unnamed
portals are automatically cleaned up after use. named statements have to be
deallocated
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On Fri, Jan 17, 2014 at 10:31 AM, Robert DiFalco
<robert(dot)difalco(at)gmail(dot)com>wrote:
> I was wondering why this setting exists and why it is by default disabled?
> Is there some danger associated with it or some reason I would NOT want it
> to be set? Thanks!
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sehrope Sarkuni | 2014-01-17 15:49:38 | Re: setPrepareThreshold |
| Previous Message | Robert DiFalco | 2014-01-17 15:31:59 | setPrepareThreshold |