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 CAA5RZ0s3wL+4RJRRtJVK1VxEgAmYrj7ftfSuAJHJ+oDfTabQbg@mail.gmail.com
Whole thread
In response to Re: Fix bug in multixact Oldest*MXactId initialization and access  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Fix bug in multixact Oldest*MXactId initialization and access
List pgsql-hackers
> > It says “Each is indexed by ProcNumber”, but it’s no longer accurate for OldestMemberMXactId prepared-xact entries,
whichnow use index (procno - FIRST_PREPARED_XACT_PROC_NUMBER). 
>
> Fixed those and some other comment work, and pushed. Thanks!
>

Thanks! what are your thoughts about adding a test like the one
here [1] ? This allows us to test correct handling of prepared
transaction dummy procs. The asserts added will not cover
this case.

What do you think?

[1] [https://www.postgresql.org/message-id/CAA5RZ0twq5bNMq0r0QNoopQnAEv%2BJ3qJNCrLs7HVqTEntBhJ%3Dg%40mail.gmail.com]

--
Sami Imseih
Amazon Web Services (AWS)



pgsql-hackers by date:

Previous
From: "Greg Burd"
Date:
Subject: Re: Expanding HOT updates for expression and partial indexes
Next
From: Tom Lane
Date:
Subject: Re: Compiler warning when using TRGM_REGEXP_DEBUG