| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, 李杰(慎追) <adger(dot)lj(at)alibaba-inc(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, 曾文旌(义从) <wenjing(dot)zwj(at)alibaba-inc(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: CREATE INDEX CONCURRENTLY on partitioned index |
| Date: | 2021-02-26 18:20:19 |
| Message-ID: | 20210226182019.GU20769@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 15, 2021 at 10:07:05PM +0300, Anastasia Lubennikova wrote:
> 5) Speaking of documentation, I think we need to add a paragraph about CIC
> on partitioned indexes which will explain that invalid indexes may appear
> and what user should do to fix them.
I'm not sure about that - it's already documented in general, for
nonpartitioned indexes.
--
Justin
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Allow-CREATE-INDEX-CONCURRENTLY-on-partitioned-table.patch | text/x-diff | 13.6 KB |
| 0002-f-progress-reporting.patch | text/x-diff | 2.5 KB |
| 0003-WIP-Add-SKIPVALID-flag-for-more-integration.patch | text/x-diff | 3.1 KB |
| 0004-ReindexPartitions-to-set-indisvalid.patch | text/x-diff | 2.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-02-26 18:55:10 | Re: Some regular-expression performance hacking |
| Previous Message | Stephen Frost | 2021-02-26 18:11:46 | Re: Interest in GSoC 2021 Projects |