Re: Update README.tuplock?

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Update README.tuplock?
Date: 2015-05-25 17:22:22
Message-ID: 55635A4E.7090506@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-05-25 17:28:02 Re: Update README.tuplock?
Previous Message Jim Nasby 2015-05-25 17:16:48 Re: xid wrap / optimize frozen tables?