Re: issue with gininsert under very high load
От | Andres Freund |
---|---|
Тема | Re: issue with gininsert under very high load |
Дата | |
Msg-id | 20140213230634.GE4910@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: issue with gininsert under very high load (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: issue with gininsert under very high load
|
Список | pgsql-hackers |
On 2014-02-13 16:15:42 -0500, Tom Lane wrote: > Heikki Linnakangas <hlinnakangas@vmware.com> writes: > > Perhaps we should use a lock to enforce that only one process tries to > > clean up the pending list at a time. > > Something like the attached? Can somebody who's seen this problem confirm > this improves matters? > > (ginInsertCleanup's header comment also needs to be rewritten, but for > testing purposes, this is fine.) Hm. Won't that possiby lead to the fast tuple list growing unboundedly? I think we would need to at least need to stop using the fast tuple mechanism during gininsert() if it's already too big and do plain inserts. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: