On Tue, Sep 30, 2014 at 1:20 AM, Craig Ringer wrote:
> Frankly, I suggest dropping "simple" entirely and using only the
> parse/bind/describe/execute flow in the v3 protocol.
The last time I checked, that was significantly slower.
http://www.postgresql.org/message-id/ca+tgmoyjkfnmrtmhodwhnoj1jwc
On Tue, Sep 30, 2014 at 11:06 AM, Tom Lane wrote:
> Shay Rojansky writes:
> > Thanks for the suggestion to look at PgJDBC, I'll do that.
>
> BTW, libpqtypes (http://libpqtypes.esilo.com) might be worth
> studying as well. I've not used it myself, but it claims to
> offer datatype-extensible pro
Shay Rojansky writes:
> Thanks for the suggestion to look at PgJDBC, I'll do that.
BTW, libpqtypes (http://libpqtypes.esilo.com) might be worth
studying as well. I've not used it myself, but it claims to
offer datatype-extensible processing of binary formats.
regards, to
Thanks for the answer Craig.
The remaining point of confusion is not really about simple vs. extended,
it's about text vs. binary. Sending parse/bind/describe/execute messages
back-to-back means the results have to be all text or all binary.
So the question is: are we supposed to transfer all typ
On 09/28/2014 05:53 PM, Shay Rojansky wrote:
> Hi.
>
> I'm a core developer on npgsql (the Postgresql .NET provider), we're
> hard at work on a major 3.0 version. I have a fundamental question
> that's been bugging me for a while and would like to get your opinion on it.
>
> Npgsql currently supp
Thanks guys, that makes perfect sense to me...
Am Sonntag, 28. September 2014 schrieb Tom Lane :
> Marko Tiikkaja > writes:
> > On 9/28/14, 11:53 AM, Shay Rojansky wrote:
> >> [ complaint about multiple round trips in extended protocol ]
>
> > You don't have to do multiple round-trips for that; y
Marko Tiikkaja writes:
> On 9/28/14, 11:53 AM, Shay Rojansky wrote:
>> [ complaint about multiple round trips in extended protocol ]
> You don't have to do multiple round-trips for that; you can just send
> all the messages in one go. See how e.g. libpq does it in PQexecParams().
Right. The k
On 9/28/14, 11:53 AM, Shay Rojansky wrote:
I would, in theory, love to switch the entire thing to binary and thereby
avoid all textual parsing once and for all. If I understand correctly, this
means all queries must be implemented as extended queries, with numerous
extra client-server roundtrips
Hi.
I'm a core developer on npgsql (the Postgresql .NET provider), we're hard
at work on a major 3.0 version. I have a fundamental question that's been
bugging me for a while and would like to get your opinion on it.
Npgsql currently supports three basic query modes: simple, client-side
parameter
