Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY |
Дата | |
Msg-id | 13733.1486317069@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY
Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY |
Список | pgsql-hackers |
Michael Paquier <michael.paquier@gmail.com> writes: > On Sun, Feb 5, 2017 at 6:53 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote: >> I agree with Pavan - a release with known important bug is not good idea. > This bug has been around for some time, so I would recommend taking > the time necessary to make the best fix possible, even if it means > waiting for the next round of minor releases. I think the way to think about this sort of thing is, if we had found this bug when a release wasn't imminent, would we consider it bad enough to justify an unscheduled release cycle? I have to think the answer for this one is "probably not". regards, tom lane
В списке pgsql-hackers по дате отправления: