| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Eric Lemoine <eric(dot)lemoine(at)oslandia(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Performance issue with Pointcloud extension |
| Date: | 2017-06-09 22:46:08 |
| Message-ID: | 2824.1497048368@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> On Fri, Jun 9, 2017 at 9:13 AM, Eric Lemoine <eric(dot)lemoine(at)oslandia(dot)com>
> wrote:
>> I now think that the performance bug is not related to the fn_extra
>> thing. I had hope but not anymore :) I don't see where the Pointcloud
>> and PostGIS extensions could conflict.
> Can you run 'perf top' on the slow query? That might pretty quickly tell
> you which function is taking up your time.
Another idea, if you haven't tried it already, is to run these test cases
in a server built with --enable-debug and --enable-cassert. The memory
clobber stuff that's enabled by the latter is very good at turning coding
errors into reproducible, debuggable crashes ;-)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | armand pirvu | 2017-06-09 22:46:26 | Re: Vacuum and state_change |
| Previous Message | Adrian Klaver | 2017-06-09 22:42:57 | Re: Vacuum and state_change |