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

From Sami Imseih
Subject Re: Fix bug in multixact Oldest*MXactId initialization and access
Date
Msg-id CAA5RZ0t8iGnqO3JcAZP1VEjCspcnZtQ0GFFVGLNLAsFqfHqRsw@mail.gmail.com
Whole thread
In response to Re: Fix bug in multixact Oldest*MXactId initialization and access  (Yura Sokolov <y.sokolov@postgrespro.ru>)
Responses Re: Fix bug in multixact Oldest*MXactId initialization and access
List pgsql-hackers
> But I still use inline procs for access to the arrays. Asserts cost nothing
> in release build. And new version of functions doesn't branch.

Asserts may have minimal impact for most builds, but my concern is
this is all unnecessary complexity. I mean if we guarantee that the
arrays are initialized correctly, maybe we can have an assert at
init time, why would we need asserts at run time?

--
Sami Imseih
Amazon Web Services (AWS)



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: PSA: Planning to grease protocol connections during 19beta
Next
From: Andres Freund
Date:
Subject: Re: More speedups for tuple deformation