| From: | Eric Lemoine <eric(dot)lemoine(at)oslandia(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Performance issue with Pointcloud extension |
| Date: | 2017-06-13 05:21:47 |
| Message-ID: | 0611113a-4288-fc32-1f8a-5cabe49bff35@oslandia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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
We found the cause of the issue! Both the PostGIS and the Pointcloud
extensions define the hexbytes_from_bytes function, and the PostGIS
version is faster. The fix involves prefixing the function name in
Pointcloud, and using a similar implementation as PostGIS [*].
Thanks a lot for helping me fix that issue.
[*] <https://github.com/pgpointcloud/pointcloud/pull/185>
--
Éric Lemoine
Oslandia
| Attachment | Content-Type | Size |
|---|---|---|
| eric_lemoine.vcf | text/x-vcard | 209 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jov | 2017-06-13 07:33:52 | Re: FULL_PAGE_WRITES |
| Previous Message | Potukanuma, Vishnu | 2017-06-13 05:03:31 | FULL_PAGE_WRITES |