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: Jeremy Schneider <schnjere@amazon.com>
Cc: "Bossart, Nathan" <bossartn@amazon.com>, Robert Haas <robertmhaas@gmail.com>, "pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>, "Nasby, Jim" <nasbyj@amazon.com>
Date: 2019-10-16T23:25:08Z
Lists: pgsql-bugs, pgsql-hackers 
On Thu, Oct 17, 2019 at 6:11 AM Jeremy Schneider <schnjere@amazon.com> wrote:
> On 10/16/19 10:09, Bossart, Nathan wrote:
> > On 10/15/19, 11:11 PM, "Thomas Munro" <thomas.munro@gmail.com> wrote:
> >> Here's a version with a proposed commit message and a comment.  Please
> >> let me know if I credited things to the right people!
> >
> > Looks good to me.  Thanks!
>
> +1

Pushed.

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