Re: Proper query implementation for Postgresql driver

From: Shay Rojansky <roji(at)roji(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Marko Tiikkaja <marko(at)joh(dot)to>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proper query implementation for Postgresql driver
Date: 2014-09-28 15:12:35
Message-ID: CADT4RqD11D8PJtRvkQ71RkGmzd+s48pa=a8bbsZ-k8oEhyMX4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks guys, that makes perfect sense to me...

Am Sonntag, 28. September 2014 schrieb Tom Lane :

> Marko Tiikkaja <marko(at)joh(dot)to <javascript:;>> 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 key thing to understand is that after an error, the server
> skips messages until it sees a Sync. So you can send out Parse, Bind,
> Execute, Sync in one packet and not have to worry that the server will
> attempt to execute a query that failed parsing or whatever.
>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-09-28 16:35:23 Re: json (b) and null fields
Previous Message Tom Lane 2014-09-28 14:41:56 Re: Patch to support SEMI and ANTI join removal