Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.
Дата
Msg-id 20200827232242.GB21986@paquier.xyz
обсуждение исходный текст
Ответ на Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-bugs
Дерево обсуждения 
On Thu, Aug 27, 2020 at 03:22:18PM -0400, Alvaro Herrera wrote:
> I first tried to add a hack directly in index_drop, but that doesn't
> really work because there's no way to tell whether the partitioned index
> is going to be dropped first or the index partition -- as that code runs
> after the dependency tree has been walked.  The condition has to be
> checked before starting the object-drop code proper.

Yes, adding that to RemoveRelations() makes sense.  Thanks for the
patch.
--
Michael
Вложения

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

Предыдущее
От: Jesse Kinkead
Дата:
Сообщение: Re: BUG #16595: Reads fail with "lost saved point in index" error after writes
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #16599: Version v4.25 is bad