From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Andrey Klychkov <aaklychkov(at)mail(dot)ru> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: |
Date: | 2020-06-02 01:32:10 |
Message-ID: | 20200602013210.GA3346@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Jun 01, 2020 at 05:39:05PM +0300, Andrey Klychkov wrote:
> I’ve seen on the internet people ask each other about this (when i
> was searching the same not seeing that in the documentation).
Note that indexes and tables can be schema-qualified in a REINDEX
query, so you would need a bit more than the query above, still you
could just wrap that in a plpgsql function that scans pg_class and
pg_index, and issues a set of DROP INDEX commands on each entry. I
have been wondering as well in the past about adding a set of SQL
queries to be able to do the work in a database as if you run into
this issue repeatedly it is annoying. So we could add that on the
reindex page close to the paragraph about the drop of invalid
indexes.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-06-02 02:47:48 | Re: pgbench bug / limitation |
Previous Message | 鄭旭宏 | 2020-06-02 01:19:32 | Re: BUG #16472: Bug in to_timestamp ? |