| 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 18:12:30 |
| Message-ID: | 20150525181230.GJ5885@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> 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.
Pushed and back-patched. I noticed that I hadn't backpatched b01a4f6838
which also updated this file, so I did so now as a single commit.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-05-25 18:14:10 | Re: fsync-pgdata-on-recovery tries to write to more files than previously |
| Previous Message | Andres Freund | 2015-05-25 18:07:06 | Re: fsync-pgdata-on-recovery tries to write to more files than previously |