Update README.tuplock?

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Update README.tuplock?
Date: 2015-05-25 09:38:51
Message-ID: 5562EDAB.3060206@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
README.tuplock-multixact-trunc.patch text/x-diff 1.4 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Emre Hasegeli 2015-05-25 10:04:18 Re: best place for "rtree" strategy numbers
Previous Message Colin 't Hart 2015-05-25 09:32:04 Re: Order of columns in query is important?!