From: Tom Lane <tgl@sss.pgh.pa.us>
To: mahendrakar s <mahendrakarforpg@gmail.com>
cc: pgsql-novice <pgsql-novice@lists.postgresql.org>
Subject: Re: Run a transaction block through SPI_execute
In-reply-to: 
 <CABkiuWqsfevi1-GzuNNeqjTMBHMN_HMUmHZOOQZBqLWcY9aU+g@mail.gmail.com>
References: 
 <CABkiuWqsfevi1-GzuNNeqjTMBHMN_HMUmHZOOQZBqLWcY9aU+g@mail.gmail.com>
Comments: In-reply-to mahendrakar s <mahendrakarforpg@gmail.com>
	message dated "Thu, 23 Nov 2023 18:33:32 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2658680.1700754465.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 23 Nov 2023 10:47:45 -0500
Message-ID: <2658681.1700754465@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2658681.1700754465%40sss.pgh.pa.us>
Precedence: bulk

mahendrakar s <mahendrakarforpg@gmail.com> writes:
> When I try to run a transaction block (similar) to below through SPI_exe=
cute:
> BEGIN; set transaction read write; ....; COMMIT
> I get an error: SPI_ERROR_TRANSACTION.
> I see that SPI interface does not support transaction manipulation comma=
nds.

Yup; you can't execute begin/commit that way.

> Transaction management support only SPI_commit/SPI_rollback.
> I'm more interested in setting `set transaction read write;` through
> SPI interface.

You could look at how plpgsql handles it.  I think though that as
long as you do BEGIN and COMMIT in the approved way, you can feed
the SET through SPI_execute or one of its siblings.

			regards, tom lane