From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Johnson <ronljohnsonjr@gmail.com>
cc: "David G. Johnston" <david.g.johnston@gmail.com>,
        Gus Spier <gus.spier@gmail.com>,
        pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: Attempting to delete excess rows from table with BATCH DELETE
In-reply-to: <CANzqJaCydWJm8utvhLMWy62MGRYP0qdK134WB8NzXTJf=KUEPg@mail.gmail.com>
References: <CAG8xnif_jmRYAGUvtoQNsHA8UqGRDkwuSffO55-3wGMLQArA8g@mail.gmail.com> <CAKFQuwbudVTMKedFTuR+GXntRM=oZ=sCgyp1Ztg2=DUciuEbQA@mail.gmail.com> <729685.1769572320@sss.pgh.pa.us> <CANzqJaCydWJm8utvhLMWy62MGRYP0qdK134WB8NzXTJf=KUEPg@mail.gmail.com>
Comments: In-reply-to Ron Johnson <ronljohnsonjr@gmail.com>
	message dated "Tue, 27 Jan 2026 23:03:46 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <731538.1769573201.1@sss.pgh.pa.us>
Date: Tue, 27 Jan 2026 23:06:41 -0500
Message-ID: <731539.1769573201@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/731539.1769573201%40sss.pgh.pa.us>
Precedence: bulk

Ron Johnson <ronljohnsonjr@gmail.com> writes:
> Hmm.  Must have been START TRANSACTION which I remember causing issues in DO
>  blocks.

Too lazy to test, but I think we might reject that.  The normal rule
in a procedure is that the next command after a COMMIT automatically
starts a new transaction, so you don't need an explicit START.

			regards, tom lane