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

From Jim Nasby
Subject Re: Update README.tuplock?
Date
Msg-id 55635A4E.7090506@BlueTreble.com
Whole thread Raw
In response to Update README.tuplock?  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: Update README.tuplock?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: xid wrap / optimize frozen tables?
Next
From: Alvaro Herrera
Date:
Subject: Re: Update README.tuplock?