Re: [HACKERS] REINDEX CONCURRENTLY 2.0
От | Andres Freund |
---|---|
Тема | Re: [HACKERS] REINDEX CONCURRENTLY 2.0 |
Дата | |
Msg-id | 1F13C8DA-D31E-4821-BA6F-0FA772AD6069@anarazel.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] REINDEX CONCURRENTLY 2.0 (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [HACKERS] REINDEX CONCURRENTLY 2.0
Re: [HACKERS] REINDEX CONCURRENTLY 2.0 |
Список | pgsql-hackers |
On March 4, 2017 1:16:56 AM PST, Robert Haas <robertmhaas@gmail.com> wrote: >Maybe. But it looks to me like this patch is going to have >considerably more than its share of user-visible warts, and I'm not >very excited about that. I feel like what we ought to be doing is >keeping the index OID the same and changing the relfilenode to point >to a newly-created one, and I attribute our failure to make that >design work thus far to insufficiently aggressive hacking. We literally spent years and a lot of emails waiting for that to happen. Users now hack up solutions like this in userspace,obviously a bad solution. 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. Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
В списке pgsql-hackers по дате отправления: