| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: issue with gininsert under very high load |
| Date: | 2014-02-13 21:15:42 |
| Message-ID: | 21759.1392326142@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)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.)
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| no-parallel-gin-cleanup.patch | text/x-diff | 1.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-02-13 22:40:13 | Re: truncating pg_multixact/members |
| Previous Message | Tom Lane | 2014-02-13 20:49:08 | Re: BUG #9210: PostgreSQL string store bug? not enforce check with correct characterSET/encoding |