Re: Partitioning table - Update on partitioning key - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: Partitioning table - Update on partitioning key
Date
Msg-id dd7389df31fe3ac9c1eac94d5ddcb2d51f453f90.camel@cybertec.at
Whole thread
In response to Re: [PATCH] Fix temporal foreign key validation of pre-existing rows  (Ewan Young <kdbase.hack@gmail.com>)
List pgsql-admin
On Thu, 2026-05-21 at 16:45 +0530, Raj wrote:
> Update happing on partition key.
>
> And we get error 'Tuple to be locked was already moved to another partition due to concurrent update error..
>
> What's the best solution to handle it?

Could you give us more context, like the exact statement and a description
of the data it is operating on?

If I had to guess, I would suspect that your UPDATE statement tries to modify
the same row more than once.

Yours,
Laurenz Albe



pgsql-admin by date:

Previous
From: Pratik Pandit
Date:
Subject: Looking for a native MongoDB document extension for PostgreSQL (similar to pgvector like extension)
Next
From: recep gül
Date:
Subject: Replica servers hanging after the latest security patch update