Re: FOR PORTION OF code review - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: FOR PORTION OF code review
Date
Msg-id a11201e5-287e-43e1-8466-4669c522942e@eisentraut.org
Whole thread
List pgsql-hackers
On 14.09.26 16:19, Peter Eisentraut wrote:
> On 14.09.26 15:52, Melanie Plageman wrote:
>> On Sat, Sep 12, 2026 at 9:18 AM Peter Eisentraut 
>> <peter@eisentraut.org> wrote:
>>>
>>> On 11.09.26 20:14, Andres Freund wrote:
>>>>> Not having a successful workaround makes it even more of a problem.
>>>>>
>>>>> Rather than forbidding READ COMMITTED at all, I think we should raise
>>>>> a serialization failure. Then the user can retry.
>>>> Personally I don't find that it's a convincing feature with that
>>>> limitation.
>>>
>>> I think we can explore different solutions, but probably not in the week
>>> before the (hopefully) last beta?
>>
>> [RMT hat]
>>
>> I don't quite understand the conclusion here. What are you proposing 
>> to do?
> 
> I was trying to nudge toward reverting without saying it. ;-)

I have reverted the feature.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Distinguish publication exclusions in object addresses
Next
From: "Chee Wooson"
Date:
Subject: [PATCH] Discard aborted updaters when expanding a multixact