No, updating the partition key (say colum created_at)....when u update the date , say change march to April, this record is in new partition and we get this error
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.
