| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: [HACKERS] REINDEX CONCURRENTLY 2.0 |
| Date: | 2018-12-07 16:40:51 |
| Message-ID: | 10797471544200851@myt3-964eae3a5b05.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 after first partitioned table in list.
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Finnerty | 2018-12-07 17:04:48 | Adding support for a fully qualified column-name in UPDATE ... SET |
| Previous Message | Pavel Stehule | 2018-12-07 16:31:04 | nice doc of PostgreSQL hooks |