Re: Partitioning table - Update on partitioning key

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Raj <rajeshkumar(dot)dba09(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Partitioning table - Update on partitioning key
Date: 2026-05-21 11:42:55
Message-ID: dd7389df31fe3ac9c1eac94d5ddcb2d51f453f90.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message recep gül 2026-05-21 12:58:39 Replica servers hanging after the latest security patch update
Previous Message Raj 2026-05-21 11:15:37 Partitioning table - Update on partitioning key