Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command - Mailing list pgsql-bugs

From Noah Misch
Subject Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command
Date
Msg-id 20250421040605.f4.nmisch@google.com
Whole thread Raw
In response to Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command  (Noah Misch <noah@leadboat.com>)
List pgsql-bugs
On Fri, Apr 11, 2025 at 07:41:33AM -0700, Noah Misch wrote:
> On Fri, Apr 11, 2025 at 10:18:04PM +0930, Robins Tharakan wrote:
> > On Thu, 23 Jan 2025 at 19:42, Richard Guo <guofenglinux@gmail.com> wrote:
> 
> > Repro SQL
> > =========
> > CREATE TEMPORARY TABLE a(b boolean , UNIQUE(b)) ON COMMIT DELETE ROWS ;
> > CREATE TEMP TABLE d() INHERITS(a) ON COMMIT DROP ;
> > ANALYSE;

> --- a/src/backend/commands/vacuum.c
> +++ b/src/backend/commands/vacuum.c
> @@ -657,6 +657,8 @@ vacuum(List *relations, VacuumParams *params, BufferAccessStrategy bstrategy,
>                  if (use_own_xacts)
>                  {
>                      PopActiveSnapshot();
> +                    /* standard_ProcessUtility() does CCI if !use_own_xacts */
> +                    CommandCounterIncrement();
>                      CommitTransactionCommand();

Pushed: postgr.es/c/2d5350c



pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: Error when using array_agg with filter where clause in pg16 and pg17
Next
From: Amit Kapila
Date:
Subject: Re: Disabled logical replication origin session causes primary key errors