Re: crash-safe visibility map, take three

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: crash-safe visibility map, take three
Дата
Msg-id 27743.1291135210@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: crash-safe visibility map, take three  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: crash-safe visibility map, take three  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: crash-safe visibility map, take three  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> That's definitely sucky, but in some ways it would be more complicated
> if they did, because I don't think all-visible on the master implies
> all-visible on the standby.

Ouch.  That seems like it could shoot down all these proposals.  There
definitely isn't any way to make VM crash-safe if there is no WAL-driven
mechanism for setting the bits.

I guess what we need is a way to delay the application of such a WAL
record on the slave until it's safe, which means the record also has to
carry some indication of the youngest XMIN on the page.
        regards, tom lane


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

Предыдущее
От: Greg Smith
Дата:
Сообщение: Re: Instrument checkpoint sync calls
Следующее
От: Robert Haas
Дата:
Сообщение: Re: crash-safe visibility map, take three