| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: issue with gininsert under very high load |
| Date: | 2014-02-13 23:49:21 |
| Message-ID: | 30461.1392335361@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-02-13 16:15:42 -0500, Tom Lane wrote:
>> Something like the attached? Can somebody who's seen this problem confirm
>> this improves matters?
> 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.
No, because we've already got a process working on cleaning it out.
In any case, this needs some testing to see if it's an improvement
or not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-02-13 23:53:43 | Re: issue with gininsert under very high load |
| Previous Message | Bruce Momjian | 2014-02-13 23:21:03 | Re: Another pgindent gripe |