| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: REINDEX CONCURRENTLY 2.0 |
| Date: | 2019-03-13 22:10:09 |
| Message-ID: | 3b33640c-5493-4eea-fd5f-71d37626fe2f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-03-13 15:13, Sergei Kornilov wrote:
> Patch is marked as target version 12, but is inactive few weeks long. I think many users want this feature and patch is in good shape. We have open questions on this thread?
>
> Latest patch still can be aplied cleanly; it builds and pass tests.
Here is an updated patch. It includes the typo fix in the documentation
from you, some small bug fixes, a new reindexdb --concurrently option,
and based on that some whole-database tests, as discussed recently.
I think this addresses all open issues.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v9-0001-REINDEX-CONCURRENTLY.patch | text/plain | 101.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-03-13 22:12:21 | Re: Inadequate executor locking of indexes |
| Previous Message | Thomas Munro | 2019-03-13 22:05:25 | Re: Using condition variables to wait for checkpoints |