| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: REINDEX CONCURRENTLY |
| Date: | 2019-03-29 08:09:27 |
| Message-ID: | 20190329080927.GB1954@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Hi Peter,
On Fri, Mar 29, 2019 at 07:26:53AM +0000, Peter Eisentraut wrote:
> REINDEX CONCURRENTLY
>
> This adds the CONCURRENTLY option to the REINDEX command. A REINDEX
> CONCURRENTLY on a specific index creates a new index (like CREATE
> INDEX CONCURRENTLY), then renames the old index away and the new index
> in place and adjusts the dependencies, and then drops the old
> index (like DROP INDEX CONCURRENTLY). The REINDEX command also has
> the capability to run its other variants (TABLE, DATABASE) with the
> CONCURRENTLY option (but not SYSTEM).
>
> The reindexdb command gets the --concurrently option.
A couple of buildfarm members using clang are not happy with this
commit:
REINDEX SCHEMA CONCURRENTLY schema_to_reindex;
+WARNING: you don't own a lock of type ShareUpdateExclusiveLock
For example longfin and dragonet:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dragonet&dt=2019-03-29%2007%3A28%3A01
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=longfin&dt=2019-03-29%2007%3A29%3A04
I cannot dig into that myself now unfortunately..
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2019-03-29 09:37:11 | Re: pgsql: Compute XID horizon for page level index vacuum on primary. |
| Previous Message | Peter Eisentraut | 2019-03-29 07:26:53 | pgsql: REINDEX CONCURRENTLY |