| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | 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-26 02:35:10 |
| Message-ID: | 20190326023510.GR2558@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 25, 2019 at 04:23:34PM +0100, Peter Eisentraut wrote:
> Let's do it. :-)
I am pretty sure that this has been said at least once since 2012.
> I've gone over this patch a few more times. I've read all the
> discussion since 2012 again and made sure all the issues were addressed.
> I made particularly sure that during the refactoring nothing in CREATE
> INDEX CONCURRENTLY and DROP INDEX CONCURRENTLY was inadvertently
> changed. I checked all the steps again. I'm happy with it.
From my side, I would be happy to look at this patch. Unfortunately I
won't have the room to look at it this week I think :(
But if you are happy with it that's fine by me, at least I can fix
anything which is broken :)
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-03-26 02:39:42 | Re: monitoring CREATE INDEX [CONCURRENTLY] |
| Previous Message | Michael Paquier | 2019-03-26 02:29:30 | Re: Special role for subscriptions |