Re: autovacuum locking question

Tom Lane <[email protected]> Fri, 06 Dec 2019 12:12:19 -0500
Newsgroups gmane.comp.db.postgresql.performance
Message-ID <[email protected]>
Mike Schanne <[email protected]> writes:
> Is this what you are referring to?
> - Prevent VACUUM from trying to freeze an old multixact ID involving a s=
till-running transaction (Nathan Bossart, Jeremy Schneider)
> This case would lead to VACUUM failing until the old transaction termina=
tes.
> https://www.postgresql.org/docs/release/9.6.16/

Hmmm ... after digging through the commit log, it seems the improvements
I was thinking of were all pre-9.6.  The only post-9.6 vacuum truncation
performance fix I can find is

https://git.postgresql.org/gitweb/?p=3Dpostgresql.git&a=3Dcommitdiff&h=3D7=
e26e02ee

which came in in v10.

			regards, tom lane