[postgis-devel] Avoid unnecessary memory copy in gserialized_datum_get_box2df_p
Paul Ramsey
pramsey at cleverelephant.ca
Wed Oct 2 09:24:41 PDT 2013
A ticket to work off of would be super.
--
Paul Ramsey
http://cleverelephant.ca
http://postgis.net
On Wednesday, October 2, 2013 at 9:04 AM, Sandro Santilli wrote:
> On Wed, Oct 02, 2013 at 08:23:49AM -0600, Paul Ramsey wrote:
> > On Wednesday, October 2, 2013 at 8:19 AM, Sandro Santilli wrote:
> > > On Wed, Oct 02, 2013 at 07:33:27AM -0600, Paul Ramsey wrote:
> > > > The reason I sliced was because we were seeing big pain for larger objects, and also because it seemed to make sense to read just a little piece rather than the whole geometry, particularly if there was a decompress step, or the whole object would have to be read into memory. What's going to happen to us for larger geometries?
> > >
> > >
> > >
> > >
> > > Reading the patch, we'd still be only slicing larger geometries.
> > > The patch basically avoids a palloc for the small geometries case.
> >
> >
> >
> > Sounds good to me then
>
> Will you apply then ?
> Sounds worth for 2.0, 2.1 and trunk...
> Need a ticket ?
>
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org (mailto:postgis-devel at lists.osgeo.org)
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
More information about the postgis-devel
mailing list