Re: Odd query execution behavior with extended protocol

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Shay Rojansky <roji(at)roji(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Charles Clavadetscher <clavadetscher(at)swisspug(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Odd query execution behavior with extended protocol
Date: 2015-10-04 16:40:32
Message-ID: 32741.1443976832@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Shay Rojansky <roji(at)roji(dot)org> writes:
>> Try adding a sync before the second execute.

> I tried inserting a Sync right before the second Execute, this caused an
> error with the message 'portal "MQ1" does not exist'.
> This seems like problematic behavior on its own, regardless of my issues
> here (Sync shouldn't be causing an implicit close of the portal, should
> it?).

Sync results in closing the transaction, if you've not explicitly executed
a BEGIN.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-10-04 16:52:22 Re: check fails on Fedora 23
Previous Message Tom Lane 2015-10-04 16:36:19 Re: Odd query execution behavior with extended protocol