Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i

Поиск
Список
Период
Сортировка
От Bossart, Nathan
Тема Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i
Дата
Msg-id 0C15CC12-F34A-4CC1-B209-9D6C92291F41@amazon.com
обсуждение исходный текст
Ответ на Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i  ("Bossart, Nathan" <bossartn@amazon.com>)
Список pgsql-committers
Дерево обсуждения 
On 12/6/17, 1:23 PM, "Bossart, Nathan" <bossartn@amazon.com> wrote:
> Perhaps this could be fixed by modifying the database-wide cases to
> use partitioned tables instead.  The individual partitions will not
> have RangeVars specified, so it would cover the case when logging
> should be skipped.

This fixed the problem for me.  I've attached a patch.

Nathan
Вложения

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updatedtuple
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple