pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: jan.mussler@zalando.de
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.
Date: Mon, 31 Aug 2020 21:30:21 -0400
Message-ID: <20200901013021.GA24136@alvherre.pgsql> (raw)
In-Reply-To: <20200901012553.GA17180@alvherre.pgsql>

Oh, and this:


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

Attachments:

docs.patch (text/x-diff, 1.1K) download
diff --git a/doc/src/sgml/ref/drop_index.sgml b/doc/src/sgml/ref/drop_index.sgml
index 0aedd71bd6..85cf23bca2 100644
--- a/doc/src/sgml/ref/drop_index.sgml
+++ b/doc/src/sgml/ref/drop_index.sgml
@@ -52,16 +52,18 @@ DROP INDEX [ CONCURRENTLY ] [ IF EXISTS ] <replaceable class="parameter">name</r
      <para>
       There are several caveats to be aware of when using this option.
       Only one index name can be specified, and the <literal>CASCADE</literal> option
       is not supported.  (Thus, an index that supports a <literal>UNIQUE</literal> or
       <literal>PRIMARY KEY</literal> constraint cannot be dropped this way.)
       Also, regular <command>DROP INDEX</command> commands can be
       performed within a transaction block, but
       <command>DROP INDEX CONCURRENTLY</command> cannot.
+      Lastly, indexes on partitioned tables cannot be dropped using this
+      option.
      </para>
      <para>
       For temporary tables, <command>DROP INDEX</command> is always
       non-concurrent, as no other session can access them, and
       non-concurrent index drop is cheaper.
      </para>
     </listitem>
    </varlistentry>

view thread (13+ messages)  latest in thread

Message-ID: <20200901013021.GA24136@alvherre.pgsql>
Permalink:  ../20200901013021.GA24136@alvherre.pgsql/
Also on:    postgresql.org/message-id/20200901013021.GA24136@alvherre.pgsql

copy link · copy postgr.es · copy git am

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: alvherre@2ndquadrant.com, michael@paquier.xyz, jan.mussler@zalando.de, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.
  In-Reply-To: <20200901013021.GA24136@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox