From: Tom Lane <tgl@sss.pgh.pa.us>
To: ganeshpandi.eswaran@chainsys.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18229: Multiple vacuum queries fail after upgrading to 13.10
In-reply-to: <18229-fc177bc9708a2787@postgresql.org>
References: <18229-fc177bc9708a2787@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 05 Dec 2023 14:22:29 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <924355.1701789973.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 05 Dec 2023 10:26:13 -0500
Message-ID: <924356.1701789973@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/924356.1701789973%40sss.pgh.pa.us>
Precedence: bulk

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-com=
mit
> 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%40postgr=
esql.org

			regards, tom lane