Re: BUG #18229: Multiple vacuum queries fail after upgrading to 13.10 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18229: Multiple vacuum queries fail after upgrading to 13.10
Date
Msg-id 924356.1701789973@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18229: Multiple vacuum queries fail after upgrading to 13.10  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> We are encountering query execution issues on Postgres versions 13.10 to 16.
> When we execute numerous vacuum queries with in-application and auto-commit
> set to false, we receive the following error.

> Error: VACUUM cannot be performed within a pipeline.

You've provided no context about how you're invoking VACUUM, but
this error message suggests that you're doing so in a way that
causes it to be run as part of a multi-command transaction.
That's always been disallowed in theory, but the enforcement
was incomplete up until our Feb 2023 releases.  You need to adjust
your application, or else convince us that whatever you're doing
should be allowed.

There's more context in this long thread:

https://www.postgresql.org/message-id/flat/17434-d9f7a064ce2a88a3%40postgresql.org

            regards, tom lane



pgsql-bugs by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: Is it possible to add support for PostgreSQL-15 and newer versions in omnipitr?
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: BUG #18213: Standby's repeatable read isolation level transaction encountered a "nonrepeatable read" problem