| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Guillaume Cottenceau *EXTERN* <gc(at)mnc(dot)ch>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: performance question: protocol v2 vs v3 |
| Date: | 2014-12-03 11:24:49 |
| Message-ID: | 547EF301.3070706@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 11/25/2014 06:45 PM, Albe Laurenz wrote:
> An explanation is maybe that prepared statements are handled
> using the extended query protocol, which only exists in v3.
> With the extended query protocol, each statement is first parsed,
> then parameters are bound to the statement and then the statement
> is executed, leading to three client-server round trips.
While Parse/Bind/Execute are separate steps, it is not correct to say
that this means three round trips.
Take a look at the conversation on the wire in Wireshark. You'll see
that generally, the Parse, Bind, Describe, Execute and Sync messages are
all actually sent in the same packet.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-12-03 11:33:40 | Re: Having issues with tests |
| Previous Message | Craig Ringer | 2014-12-03 11:22:30 | Re: Fwd: [GENERAL] Trying to get SSPI/JDBC working |