Horton

Re: ERROR: multixact X from before cutoff Y found to be still running

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: "Bossart, Nathan" <bossartn@amazon.com>, "Schneider, Jeremy" <schnjere@amazon.com>, "pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>, "Nasby, Jim" <nasbyj@amazon.com>
Date: 2019-09-06T20:40:53Z
Lists: pgsql-bugs, pgsql-hackers 
On Sat, Sep 7, 2019 at 5:25 AM Robert Haas <robertmhaas@gmail.com> wrote:
> (I apologize if any of the above sounds like I'm talking credit for
> work actually done by Thomas, who I see is listed as the primary
> author of the commit in question.  I feel like I invented
> MultiXactMemberFreezeThreshold and the big comment at the top of it
> looks to me like something I wrote, but but this was a long time ago
> and I don't really remember who did what. My intent here is to provide
> some context that may be useful based on what I remember about that
> patch, not to steal anybody's thunder.)

I don't recall but it could well have been your idea to do it that
way, my code and testing, and your comments and commit.  Either way
I'm happy for you to steal my bugs.

-- 
Thomas Munro
https://enterprisedb.com

Commits

  1. Fix bug that could try to freeze running multixacts.

  2. Teach autovacuum about multixact member wraparound.

  3. Separate multixact freezing parameters from xid's