Re: Update README.tuplock?

Поиск
Список
Период
Сортировка
От Jim Nasby
Тема Re: Update README.tuplock?
Дата
Msg-id 55635A4E.7090506@BlueTreble.com
обсуждение исходный текст
Ответ на Update README.tuplock?  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Ответы Re: Update README.tuplock?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
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.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



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

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: xid wrap / optimize frozen tables?
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Update README.tuplock?