| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ganeshpandi(dot)eswaran(at)chainsys(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18229: Multiple vacuum queries fail after upgrading to 13.10 |
| Date: | 2023-12-05 15:26:13 |
| Message-ID: | 924356.1701789973@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2023-12-06 02:32:35 | Re: BUG #18213: Standby's repeatable read isolation level transaction encountered a "nonrepeatable read" problem |
| Previous Message | hubert depesz lubaczewski | 2023-12-05 14:48:43 | Re: Is it possible to add support for PostgreSQL-15 and newer versions in omnipitr? |