From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Subject: | Re: REINDEX CONCURRENTLY 2.0 |
Date: | 2017-03-05 18:56:55 |
Message-ID: | CA+TgmoZXmKOCe5FezHF3n-KLk56Ea-N0DW6zYGGWDCz2jDXzNw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 4, 2017 at 12:34 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I agree that'd it be nicer not to have this, but not having the feature at all is a lot worse than this wart.
I, again, give that a firm "maybe". If the warts end up annoying 1%
of the users who try to use this feature, then you're right. If they
end up making a substantial percentage of people who try to use this
feature give up on it, then we've added a bunch of complexity and
future code maintenance for little real gain. I'm not ruling out the
possibility that you're 100% correct, but I'm not nearly as convinced
of that as you are.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2017-03-05 21:07:07 | Re: Faster methods for getting SPI results |
Previous Message | Craig Ringer | 2017-03-05 14:22:56 | Re: Measuring replay lag |