Re: Fix bug in multixact Oldest*MXactId initialization and access - Mailing list pgsql-hackers

From Yura Sokolov
Subject Re: Fix bug in multixact Oldest*MXactId initialization and access
Date
Msg-id 3d7a2207-0e61-4d95-bc00-e5248956a32b@postgrespro.ru
Whole thread Raw
In response to Re: Fix bug in multixact Oldest*MXactId initialization and access  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Fix bug in multixact Oldest*MXactId initialization and access
List pgsql-hackers
26.02.2026 23:44, Sami Imseih пишет:
>> (Sorry, I've used Google Translate to write this sentence).
>>
>> When you write assert, you protect yourself from shooting your leg far in
>> the future. Believe me.
> 
> The issue to me seems that we a few code paths that rely on the
> total proc calculation in several places, and changing one and
> forgetting to change another is what broke things.

If there were asserts, then tests would have failed.
Period.

There would no the bug. There would no this discussion.
If only array bounds were checked with asserts.

-- 
regards
Yura Sokolov aka funny-falcon



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: Defects with invalid stats data for expressions in extended stats
Next
From: Bertrand Drouvot
Date:
Subject: Re: Adding locks statistics