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
Date: Mon, 27 Feb 2023 11:34:16 -0500
Message-ID: <371962.1677515656@sss.pgh.pa.us> (raw)
In-Reply-To: <17810-8eb7b4e1b7a68e1a@postgresql.org>
References: <17810-8eb7b4e1b7a68e1a@postgresql.org>
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
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, cherio@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
In-Reply-To: <371962.1677515656@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