Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently - Mailing list pgsql-bugs

From Alexander Lakhin
Subject Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
Date
Msg-id d85fb492-5c99-245d-a4a0-ea47b5610dd9@gmail.com
Whole thread Raw
In response to Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List 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



pgsql-bugs by date:

Previous
From: Francisco Olarte
Date:
Subject: Re: BUG #17793: Query with large number of joins crashes PostgreSQL
Next
From: Dean Rasheed
Date:
Subject: Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently