| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Scott Harrington <scotth01(at)sns-usa(dot)com>, Mikko Tiihonen <Mikko(dot)Tiihonen(at)nitorcreations(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: [JDBC] Pipelining executions to postgresql server |
| Date: | 2014-11-04 07:21:51 |
| Message-ID: | 54587E8F.5060206@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On 11/03/2014 07:05 AM, Scott Harrington wrote:
> I looked over your patch. Your list of ResultHandlerHolders seems to be
> the right direction, but as Tom Lane mentioned there may need to be some
> way to ensure the statements are all in the same transaction.
Why go down this track, when we already have batching?
Just use the standard JDBC API batching facilities and add the missing
support for batching queries that return result sets in PgJDBC.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-11-04 07:28:46 | Re: [HACKERS] Pipelining executions to postgresql server |
| Previous Message | CK Tan | 2014-11-04 07:11:54 | Re: Let's drop two obsolete features which are bear-traps for novices |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-11-04 07:28:46 | Re: [HACKERS] Pipelining executions to postgresql server |
| Previous Message | Craig Ringer | 2014-11-04 01:56:17 | Re: [HACKERS] Pipelining executions to postgresql server |