Re: Update README.tuplock?

Поиск
Список
Период
Сортировка
От Amit Langote
Тема Re: Update README.tuplock?
Дата
Msg-id 5563BBDD.3020906@lab.ntt.co.jp
обсуждение исходный текст
Ответ на Re: Update README.tuplock?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
On 2015-05-26 AM 03:12, Alvaro Herrera wrote:
> 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.
> 

Thanks!

Amit




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Run pgindent now?
Следующее
От: Robert Haas
Дата:
Сообщение: Re: fsync-pgdata-on-recovery tries to write to more files than previously