Re: Update README.tuplock?
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Update README.tuplock? |
| Дата | |
| Msg-id | 20150525172802.GH5885@postgresql.org обсуждение исходный текст |
| Ответ на | Re: Update README.tuplock? (Jim Nasby <Jim.Nasby@BlueTreble.com>) |
| Ответы |
Re: Update README.tuplock?
|
| Список | 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
В списке pgsql-hackers по дате отправления: