Re: [HACKERS] REINDEX CONCURRENTLY 2.0 - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: [HACKERS] REINDEX CONCURRENTLY 2.0
Date
Msg-id 10797471544200851@myt3-964eae3a5b05.qloud-c.yandex.net
Whole thread Raw
In response to Re: [HACKERS] REINDEX CONCURRENTLY 2.0  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] REINDEX CONCURRENTLY 2.0  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Hello

Thank you for working on this patch!

I perform some tests and think behavior with partition tables is slightly inconsistent.

postgres=# reindex table measurement;
WARNING:  REINDEX of partitioned tables is not yet implemented, skipping "measurement"
NOTICE:  table "measurement" has no indexes
REINDEX
postgres=# reindex table CONCURRENTLY measurement;
ERROR:  cannot reindex concurrently this type of relation

Maybe we need report warning and skip partitioned tables similar to plain reindex?

This makes more sense for "reindex database" or "reindex schema": as far i can see, concurrent reindex will stop work
afterfirst partitioned table in list.
 

regards, Sergei


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: nice doc of PostgreSQL hooks
Next
From: Jim Finnerty
Date:
Subject: Adding support for a fully qualified column-name in UPDATE ... SET