On 5/25/15 4:38 AM, Amit Langote wrote:
Commit f741300c90141ee274f19a13629ae03a9806b598 ("Have multixact be truncated by checkpoint, not vacuum") changed who truncates multixact. README.tuplock still says VACUUM is in charge of the truncation. I think it's an oversight in updating the README unless I am missing something.I attempted to fix it as attached. See if that makes sense.
Looks good and is AFAIK correct. -- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
