pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brar Piening <brar@gmx.de>
Cc: mike.adelson314@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16988: Spurious "SET LOCAL can only be used in transaction blocks" warning using implicit transaction block
Date: Sat, 01 May 2021 19:35:55 -0400
Message-ID: <3493686.1619912155@sss.pgh.pa.us> (raw)
In-Reply-To: <3a158f8d-708e-ad13-617a-af8349aae4f4@gmx.de>
References: <16988-58edba102adb5128@postgresql.org>
	<3044772.1619712195@sss.pgh.pa.us>
	<3a158f8d-708e-ad13-617a-af8349aae4f4@gmx.de>

Brar Piening <brar@gmx.de> writes:
> Tom Lane wrote:
>> PG Bug reporting form <noreply@postgresql.org> writes:
>>> I am using SET LOCAL in an Npgsql multi-statement command.

>> It seems that whatever Npgsql is doing at the wire protocol level
>> doesn't match this, but they'd have to explain what they are doing
>> for us to offer much help.

> At the wire protocol level npgsql sends this as two queries via the
> extended query protocol without a sync inbetween them.
> (Parse,Bind,Describe,Execute;Parse,Bind,Describe,Execute,Sync)

There is no implicit transaction block around the two commands in such
a case, so that explains why it doesn't act as Mike was hoping.

Omitting the Sync has zero effect on transactional semantics; it only
means that if the first command fails, we'll skip the second one.

			regards, tom lane





view thread (5+ messages)  latest in thread

Message-ID: <3493686.1619912155@sss.pgh.pa.us>
Permalink:  ../3493686.1619912155@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3493686.1619912155@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, brar@gmx.de, mike.adelson314@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16988: Spurious "SET LOCAL can only be used in transaction blocks" warning using implicit transaction block
  In-Reply-To: <3493686.1619912155@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox