| From: | Raj <rajeshkumar(dot)dba09(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Partitioning table - Update on partitioning key |
| Date: | 2026-05-21 16:11:55 |
| Message-ID: | CAJk5AtYo4hUFwpKwZGpSzPG3ruTgRPLaKXyVOYn=JGoN29u+Qw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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, 21 May 2026, 17:12 Laurenz Albe, <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2026-05-21 17:50:21 | Re: Partitioning table - Update on partitioning key |
| Previous Message | recep gül | 2026-05-21 14:09:24 | Ynt: Replica servers hanging after the latest security patch update |