[postgis-devel] How about a 3.3.4 release, for topology improvements ?

Regina Obe lr at pcorp.us
Thu Jul 6 11:40:19 PDT 2023


I'm okay with a 3.3.4 release too strk, especially since you are offering :)


@Paul -- I put wagyu as a breaking change just cause I felt it was functionality that some people
Might miss and wanted to alert them.  Then again like you said, it's unlikely the MVT stuff was taking enough time to warrant an interruption
Except for those ones that pull the whole planet into one tile. If you feel it's causing more scare than benefit, feel free to take that part out.

Thanks,
Regina

> -----Original Message-----
> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On
> Behalf Of Paul Ramsey
> Sent: Thursday, July 6, 2023 12:26 PM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> Subject: Re: [postgis-devel] How about a 3.3.4 release, for topology
> improvements ?
> 
> I’m always fine w/ a maintenance release.
> Not sure that the wagyu interrupt thing is a “breaking change”, not sure what
> it would break, it just means there might be slightly more delay in an
> interrupt in the very rare case that wagyu is actually taking a lot of time.
> 
> P
> 
> > On Jul 6, 2023, at 9:24 AM, Sandro Santilli <strk at kbt.io> wrote:
> >
> > There's a serious topology bug fixed in the 3.3 branch which didn't
> > make it into 3.3.3, plus a few more:
> >
> >  * Bug Fixes and Enhancements *
> >    - #5395, [postgis_topology] Allow unprivileged user dump
> >             of database with topology enabled
> >    - #5394, [postgis_topology] Improve robustness of finding
> >             distinct vertices in topology edges (Sandro Santilli)
> >    - #5403, [postgis_topology] Fix ValidateTopology(bbox) without
> >             topology in search_path (Sandro Santilli)
> >    - #5410, [postgis_raster] ST_Value bilinear resample,
> >             don't throw an error if Band has no NODATA value
> >             (Regina Obe)
> >    - #5385, Postgres malloc assertion fail when
> >             using pg_cancel_backend with ST_AsMVT
> >             (Regina Obe, Paul Ramsey)
> >
> >  * Breaking Changes *
> >      - #5385, Take out interruptability of ST_AsMVT
> >               as it causes backend crash under intense conditions
> >              (Regina Obe, Paul Ramsey)
> >
> > Trac is 1 ticket left 3.3.4:
> >
> >
> > https://trac.osgeo.org/postgis/query?status=assigned&status=new&status
> > =reopened&milestone=PostGIS+3.3.4&group=status&order=priority
> >
> >  - #5408   regression failure on tiger geocoder pagc_normalize_address
> >
> > Are you ok with pushing that forward and cutting a 3.3.4 releease ?
> > I can do it, if you're ok with it. Note that #5395 was a regression
> > introduced in 3.3.3 (not present in 3.3.2).
> >
> > --strk;
> >
> >  Libre GIS consultant/developer
> >  https://strk.kbt.io/services.html
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/postgis-devel
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel



More information about the postgis-devel mailing list