Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
Date: 2023-02-14 12:00:00
Message-ID: d85fb492-5c99-245d-a4a0-ea47b5610dd9@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello Alvaro,
14.02.2023 14:29, Alvaro Herrera wrote:
> Hmm, yeah: because this is not a partitioned table, we are definitely
> not expecting that cpUpdateRetrySlot will be set. Can you still
> reproduce the problem with the attached patch?
No, your patch fixes the issue.
Thanks for looking at this!

Best regards,
Alexander

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2023-02-14 12:05:35 Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
Previous Message Francisco Olarte 2023-02-14 11:51:02 Re: BUG #17793: Query with large number of joins crashes PostgreSQL