Update README.tuplock? - Mailing list pgsql-hackers

From Amit Langote
Subject Update README.tuplock?
Date
Msg-id 5562EDAB.3060206@lab.ntt.co.jp
Whole thread Raw
Responses Re: Update README.tuplock?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Hi,

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.

Thanks,
Amit

Attachment

pgsql-hackers by date:

Previous
From: "Colin 't Hart"
Date:
Subject: Re: Order of columns in query is important?!
Next
From: Emre Hasegeli
Date:
Subject: Re: best place for "rtree" strategy numbers