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

From Albe Laurenz
Subject Re: performance question: protocol v2 vs v3
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17DA76B4@ntex2010a.host.magwien.gv.at
Whole thread Raw
In response to Re: performance question: protocol v2 vs v3  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: performance question: protocol v2 vs v3  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-jdbc
Craig Ringer wrote:
> 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.

I didn't know that, thanks for the clarification.

Yours,
Laurenz Albe

pgsql-jdbc by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Having issues with tests
Next
From: Craig Ringer
Date:
Subject: Re: performance question: protocol v2 vs v3