Re: Freeze avoidance of very large table.

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Freeze avoidance of very large table.
Дата
Msg-id 20151217071049.GJ23112@awork2.anarazel.de
обсуждение исходный текст
Ответ на Re: Freeze avoidance of very large table.  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: Freeze avoidance of very large table.  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
On 2015-12-17 15:56:35 +0900, Michael Paquier wrote:
> On Thu, Dec 17, 2015 at 3:44 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> > For me, rewriting the visibility map is a new data loss bug waiting to
> > happen. I am worried that the group is not taking seriously the potential
> > for catastrophe here.
> 
> FWIW, I'm following this line and merging the vm file into a single
> unit looks like a ticking bomb.

And what are those risks?

> We may really want a separate _vm file, like _vmf to track this new
> bit flag but this has already been mentioned largely upthread...

That'd double the overhead when those bits get unset.



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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Freeze avoidance of very large table.
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Refactoring speculative insertion with unique indexes a little