Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher
Дата
Msg-id CABOikdNKDsuStsU+uJ-HraD1+xDb6aRJ9mJeQehYE-znAZ5PFg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
Дерево обсуждения


On Fri, May 5, 2017 at 10:56 AM, Michael Paquier <michael.paquier@gmail.com> wrote:
On Wed, May 3, 2017 at 12:25 AM, Peter Eisentraut


>>> Can we prevent HOT pruning during logical decoding?
>>
>> It does not sound much difficult to do, couldn't you just make it a
>> no-op with am_walsender?
>
> That's my hope.

The only code path doing HOT-pruning and generating WAL is
heap_page_prune(). Do you think that we need to worry about FPWs as
well?

IMO the check should go inside heap_page_prune_opt(). Do we need to worry about wal_log_hints or checksums producing WAL because of hint bit updates? While I haven't read the thread, I am assuming if HOT pruning can happen, surely hint bits can get set too.

Thanks,
Pavan
 
--
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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

Предыдущее
От: 甄明洋
Дата:
Сообщение: [HACKERS] May cause infinite loop when initializing rel-cache containspartitioned table
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: [HACKERS] Error message on missing SCRAM authentication witholder clients