| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: reindexing db |
| Date: | 2020-12-08 01:00:42 |
| Message-ID: | CAKFQuwb_6QWgSmUn-G2qEqmHWU1fychQuJrOZ_bF0ofCE0a_gg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Dec 7, 2020 at 5:45 PM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> Does reindexdb --concurrently skip over indexes for exclusion constraints,
> or reindex them separately without the concurrently option? The docs for
> reindexdb simply point one to the reindex docs for the caveats of
> concurrently, where that restriction is mentioned.
>
>
The REINDEX page says:
"Furthermore, indexes for exclusion constraints cannot be reindexed
concurrently. If such an index is named directly in this command, an error
is raised. If a table or database with exclusion constraint indexes is
reindexed concurrently, those indexes will be skipped. (It is possible to
reindex such indexes without the CONCURRENTLY option.)"
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2020-12-08 02:07:28 | Re: reindexing db |
| Previous Message | Scott Ribe | 2020-12-08 00:45:46 | reindexing db |