| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | 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: Pipelining executions to postgresql server |
| Date: | 2014-11-01 17:31:16 |
| Message-ID: | 20141101173116.GR13584@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On 2014-11-01 14:04:05 +0000, Mikko Tiihonen wrote:
> I created a proof of concecpt patch for postgresql JDBC driver that
> allows the caller to do pipelining of requests within a
> transaction. The pipelining here means same as for HTTP: the client
> can send the next execution already before waiting for the response of
> the previous request to be fully processed.
Slightly confused here. To my knowledge the jdbc driver already employs
some pipelining? There's some conditions where it's disabled (IIRC
RETURNING for DML is one of them), but otherwise it's available.
I'm very far from a pgjdbc expert, but that's what I gathered from the
code when investigating issues a while back and from my colleague Craig.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-11-01 17:35:42 | Re: tracking commit timestamps |
| Previous Message | Tom Lane | 2014-11-01 17:30:46 | Re: Let's drop two obsolete features which are bear-traps for novices |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikko Tiihonen | 2014-11-02 12:11:49 | Re: [HACKERS] Pipelining executions to postgresql server |
| Previous Message | Tom Lane | 2014-11-01 16:13:03 | Re: Pipelining executions to postgresql server |