Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock
От | Alexander Korotkov |
---|---|
Тема | Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock |
Дата | |
Msg-id | CAPpHfds7QYCsKm5bj+WB2FweuxuZZBhkXwZhy8Sbzav=RHL35w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock (Alexander Korotkov <aekorotkov@gmail.com>) |
Ответы |
Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock
|
Список | pgsql-hackers |
On Fri, Mar 22, 2019 at 11:05 AM Alexander Korotkov <aekorotkov@gmail.com> wrote: > On Fri, Mar 22, 2019 at 12:06 AM Alvaro Herrera > <alvherre@2ndquadrant.com> wrote: > > On 2019-Mar-21, Alexander Korotkov wrote: > > > > > However, I think this still can be backpatched correctly. We can > > > determine whether xlog record data contains deleteXid by its size. > > > See the attached patch. I haven't test this yet. I'm going to test > > > it. If OK, then push. > > > > Wow, this is so magical that I think it merits a long comment explaining > > what is going on. > > Yeah, have to fo magic to fix such weird things :) > Please, find next revision of patch attached. It uses static > assertion to check that data structure size has changed. Also, > assertion checks that record data length match on of structures > length. I'm going to backpatch this on no objections. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
В списке pgsql-hackers по дате отправления: