Re: performance question: protocol v2 vs v3 - Mailing list pgsql-jdbc

From Craig Ringer
Subject Re: performance question: protocol v2 vs v3
Date
Msg-id 547EF301.3070706@2ndquadrant.com
Whole thread Raw
In response to Re: performance question: protocol v2 vs v3  (Albe Laurenz <laurenz.albe@wien.gv.at>)
Responses Re: performance question: protocol v2 vs v3
List 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


pgsql-jdbc by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Fwd: [GENERAL] Trying to get SSPI/JDBC working
Next
From: Craig Ringer
Date:
Subject: Re: Having issues with tests