Re: GIN data corruption bug(s) in 9.6devel
От
Alvaro Herrera
Тема
Re: GIN data corruption bug(s) in 9.6devel
Дата
Msg-id
20160407222302.GA605634@alvherre.pgsql
Ответ на
Re: GIN data corruption bug(s) in 9.6devel (Jeff Janes)
Список
Дерево обсуждения
Re: GIN data corruption bug(s) in 9.6devel Tomas Vondra <tomas.vondra@2ndquadrant.com>
Re: GIN data corruption bug(s) in 9.6devel Teodor Sigaev <teodor@sigaev.ru>
Re: GIN data corruption bug(s) in 9.6devel Jeff Janes <jeff.janes@gmail.com>
Re: GIN data corruption bug(s) in 9.6devel Alvaro Herrera <alvherre@2ndquadrant.com>
Re: GIN data corruption bug(s) in 9.6devel Tom Lane <tgl@sss.pgh.pa.us>
Re: GIN data corruption bug(s) in 9.6devel Jeff Janes <jeff.janes@gmail.com>
Re: GIN data corruption bug(s) in 9.6devel Noah Misch <noah@leadboat.com>
Re: GIN data corruption bug(s) in 9.6devel Teodor Sigaev <teodor@sigaev.ru>
Re: GIN data corruption bug(s) in 9.6devel Teodor Sigaev <teodor@sigaev.ru>
Re: GIN data corruption bug(s) in 9.6devel Jeff Janes <jeff.janes@gmail.com>
Re: GIN data corruption bug(s) in 9.6devel Teodor Sigaev <teodor@sigaev.ru>
Re: GIN data corruption bug(s) in 9.6devel Noah Misch <noah@leadboat.com>
Re: GIN data corruption bug(s) in 9.6devel Jeff Janes <jeff.janes@gmail.com>
Re: GIN data corruption bug(s) in 9.6devel Noah Misch <noah@leadboat.com>
Re: GIN data corruption bug(s) in 9.6devel Teodor Sigaev <teodor@sigaev.ru>
Re: GIN data corruption bug(s) in 9.6devel Jeff Janes <jeff.janes@gmail.com>
Re: GIN data corruption bug(s) in 9.6devel Teodor Sigaev <teodor@sigaev.ru>
Re: GIN data corruption bug(s) in 9.6devel Noah Misch <noah@leadboat.com>
Re: GIN data corruption bug(s) in 9.6devel Robert Haas <robertmhaas@gmail.com>
Re: GIN data corruption bug(s) in 9.6devel Teodor Sigaev <teodor@sigaev.ru>
Jeff Janes wrote: > The proposed change removes that throttle, so that inserters will > immediately see there is already a cleaner and just go back about > their business. Due to that, unthrottled backends could add to the > pending list faster than the cleaner can clean it, leading to > unbounded growth in the pending list and could cause a user backend to > becoming apparently unresponsive to the user, indefinitely. That is > scary to backpatch. Can we install a protection against that? For instance, the cleaner only cleans up the entries that were present when it started, and if other items are inserted later into the pending list, they are left for a future cleaner. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления