| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | 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:28:02 |
| Message-ID: | 20150525172802.GH5885@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-25 17:28:16 | Re: Run pgindent now? |
| Previous Message | Jim Nasby | 2015-05-25 17:22:22 | Re: Update README.tuplock? |