Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message. - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.
Date
Msg-id 20200827172519.GA5940@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
Tree view 
On 2020-Aug-27, Michael Paquier wrote:

> The error message is really confusing though, so for now I would
> recommend to just drop an error if trying the operation on a
> partitioned table, and we also do that now for CREATE INDEX
> CONCURRENTLY.

Yeah, let's throw an error if the table is partitioned.  My bug -- I'll
go fix it now.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16595: Reads fail with "lost saved point in index" error after writes
Next
From: PG Bug reporting form
Date:
Subject: BUG #16598: SharedFileSetCreate doesn't handle PathNameCreateTemporaryFile failure correctly