From: Tom Lane <tgl@sss.pgh.pa.us>
To: cherio@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
In-reply-to: <17810-8eb7b4e1b7a68e1a@postgresql.org>
References: <17810-8eb7b4e1b7a68e1a@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 27 Feb 2023 15:27:42 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <371961.1677515656.1@sss.pgh.pa.us>
Date: Mon, 27 Feb 2023 11:34:16 -0500
Message-ID: <371962.1677515656@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/371962.1677515656%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> My system has numerous SQL scripts (each script contains multiple SQL
> statements). Many of them look like

> UPDATE ...
> INSERT ...
> ...
> VACUUM ...

> These scripts are being run from a Java program, with AutoCommit=true, via
> JDBC as:

Sorry, you'll have to fix your scripts to do that separately.
(It might be sufficient to add COMMIT before the VACUUM.)
It was a bug that we didn't enforce this requirement all along.

> The same SQL scripts are still working with the latest postgresql 14.7

I'm quite skeptical of that claim; I see the restriction being
enforced the same way in all supported branches.

			regards, tom lane