Re: [HACKERS] REINDEX CONCURRENTLY 2.0

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