From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Performance bug in prepared statement binding in 9.2? |
Date: | 2013-09-10 12:45:33 |
Message-ID: | 522F146D.2070908@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 09/10/2013 08:20 AM, Andres Freund wrote:
> A backtrace for this would be useful. Alternatively you could recompile
> postgres using -fno-omit-frame-pointer in CFLAGS and use perf record -g.
It's using a custom build, so this should be doable.
>
> Any chance you have older prepared xacts, older sessions or something
> like that around? I'd expect heap_prune* to be present in workloads that
> spend significant time in heap_hot_search_buffer...
Not sure about prepared transactions. There are certainly probably old
prepared statements around, and long running transactions alongside this
one.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-09-10 13:21:33 | Re: Performance bug in prepared statement binding in 9.2? |
Previous Message | Andres Freund | 2013-09-10 12:32:07 | Re: Performance bug in prepared statement binding in 9.2? |