Re: Update README.tuplock? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Update README.tuplock?
Date
Msg-id 20150525172802.GH5885@postgresql.org
Whole thread Raw
In response to Re: Update README.tuplock?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Update README.tuplock?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Jim Nasby wrote:
> 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.

No, it's wrong .. Will push a fix, thanks.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Update README.tuplock?
Next
From: Tom Lane
Date:
Subject: Re: Run pgindent now?