Re: pg_multixact not getting truncated

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема Re: pg_multixact not getting truncated
Дата
Msg-id 546D08B3.9010306@agliodbs.com
обсуждение исходный текст
Ответ на Re: pg_multixact not getting truncated  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: pg_multixact not getting truncated  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 11/19/2014 01:03 PM, Alvaro Herrera wrote:
> Josh Berkus wrote:
>> On 11/12/2014 06:57 PM, Alvaro Herrera wrote:
>>>> How did template0 even get a MultiXact? That sounds like they're really abusing the template databases. :( (Do
keepin mind that MXID 1 is a special value.)
 
>>> No, it's normal -- template0 does not have a multixact in any tuple's
>>> xmax, but datminxid is set to the value that is current when it is
>>> frozen.
>>
>> So, to follow up on this: it seems to me that we shouldn't be requiring
>> freezing for databases where allowconn=false.  This seems like a TODO to
>> me, even possibly a backpatchable bug fix.
> 
> Why do we need this for pg_multixact but not for pg_clog?

I think we want it for both.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: pg_multixact not getting truncated
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Increasing test coverage of WAL redo functions