Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cherio(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
Date: 2023-02-27 16:34:16
Message-ID: 371962.1677515656@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Cherio 2023-02-27 17:31:21 Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
Previous Message Cherio 2023-02-27 16:28:37 Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM