PostGIS 2.3.1 released

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

PostGIS 2.3.1 released

Regina Obe
The PostGIS development team is happy to release PostGIS 2.3.1.
This is best served with pgRouting 2.3.1 (which was released last week:
https://github.com/pgRouting/pgrouting/releases/tag/v2.3.1 )
As befits a patch release, the focus is on bugs and breakages.

Source: http://download.osgeo.org/postgis/source/postgis-2.3.1.tar.gz

Docs PDF:  http://download.osgeo.org/postgis/docs/postgis-2.3.1.pdf

Doc Html: http://download.osgeo.org/postgis/docs/doc-html-2.3.1.tar.gz

Details of what got fixed, improved:

  - #1973, st_concavehull() returns sometimes empty geometry collection
           Fix from gde
  - #3501, add raster constraint max extent exceeds array size limit
        for large tables
  - #3643, PostGIS not building on latest OSX XCode
  - #3644, Deadlock on interrupt
  - #3650, Mark ST_Extent, ST_3DExtent and ST_Mem*
        agg functions as parallel safe so they can be parallelized
  - #3652, Crash on Collection(MultiCurve())
  - #3656, Fix upgrade of aggregates from 2.2 or lower version
  - #3659, Crash caused by raster GUC define after CREATE EXTENSION
     using wrong memory context. (manaeem)
  - #3665, Index corruption and memory leak in BRIN indexes
    patch from Julien Rouhaud (Dalibo)
  - #3667, geography ST_Segmentize bug
    patch from Hugo Mercier (Oslandia)

Thanks,

PostGIS development Team

_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|

Re: PostGIS 2.3.1 released

Stephen Frost
Regina, all

* Regina Obe ([hidden email]) wrote:
> The PostGIS development team is happy to release PostGIS 2.3.1.
> This is best served with pgRouting 2.3.1 (which was released last week:
> https://github.com/pgRouting/pgrouting/releases/tag/v2.3.1 )
> As befits a patch release, the focus is on bugs and breakages.

Not sure if anyone else is seeing this, but if I go to the news page:

http://postgis.org/news/20161128/

and then click on the 'now available' link, I get:

http://download.osgeo.org/postgis/source/postgis-2.3.1.tar.gz/

Which returns:

-----
Not Found
The requested URL /postgis/source/postgis-2.3.1.tar.gz/ was not found on
this server.
-----

Looks like someone added a trailing '/' by mistake somehow.

Thanks!

Stephen

_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: PostGIS 2.3.1 released

Sandro Santilli-4
On Fri, Dec 02, 2016 at 09:42:18AM -0500, Stephen Frost wrote:
>
> Not sure if anyone else is seeing this, but if I go to the news page:
>
> http://postgis.org/news/20161128/

The official website has correct links:
 http://postgis.net/
 http://postgis.net/source/

The .org website can only be corrected by Refractions guys, I'm not
sure if anyone still reads this mailing list.

--strk;
_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|

Postgis 2.3.1 regression test failure on NetBSD-7 amd64

Greg Troxel-2
In reply to this post by Regina Obe
I am updating pkgsrc to 2.3.1 (from 2.2.2), and I got a regression test
failure.  This is with gcc 4.8 and postgresql 9.3.  Everything else
seems ok.    I wonder if this is a situation where a range of behavior
is acceptable, and the test has a limit, or if this indicates that
something really is wrong.   The test cluster was on a spinning disk
that also holds src/obj for an OS recompile, so this isn't a
particularly high-performance setup.


--- interrupt_relate_expected   2015-08-04 05:08:19.000000000 -0400
+++ /tmp/pgis_reg/test_108_out  2016-12-05 10:00:47.000000000 -0500
@@ -1,5 +1,5 @@
 ERROR:  canceling statement due to statement timeout
-contains interrupted on time
+contains interrupted late: 00:00:00.274858
 ERROR:  canceling statement due to statement timeout
 covers interrupted on time
 ERROR:  canceling statement due to statement timeout
_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|

Re: Postgis 2.3.1 regression test failure on NetBSD-7 amd64

Sandro Santilli-4
On Mon, Dec 05, 2016 at 10:06:42AM -0500, Greg Troxel wrote:

> -contains interrupted on time
> +contains interrupted late: 00:00:00.274858

Nothing to worry about, unfortunately we do have some time-sensitive
tests so if the tester does not receive enough timeslots it may end
up interrupting later than expected.

I'd love to fix these but hadn't found a way to obtain CPU time
of a postgresql session.

--strk;
_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|

Re: Postgis 2.3.1 regression test failure on NetBSD-7 amd64

Stephen Woodbridge
On 12/5/2016 12:21 PM, Sandro Santilli wrote:

> On Mon, Dec 05, 2016 at 10:06:42AM -0500, Greg Troxel wrote:
>
>> -contains interrupted on time
>> +contains interrupted late: 00:00:00.274858
>
> Nothing to worry about, unfortunately we do have some time-sensitive
> tests so if the tester does not receive enough timeslots it may end
> up interrupting later than expected.
>
> I'd love to fix these but hadn't found a way to obtain CPU time
> of a postgresql session.

Can't you do something like, get the pid of the backend process and then
use a system call to get the cpu time maybe using via /proc/[PID]/stat
on linux

and maybe something like this on Windows:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms683223(v=vs.85).aspx

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|

Re: Postgis 2.3.1 regression test failure on NetBSD-7 amd64

Sandro Santilli-4
On Mon, Dec 05, 2016 at 01:33:40PM -0500, Stephen Woodbridge wrote:

> On 12/5/2016 12:21 PM, Sandro Santilli wrote:
> >On Mon, Dec 05, 2016 at 10:06:42AM -0500, Greg Troxel wrote:
> >
> >>-contains interrupted on time
> >>+contains interrupted late: 00:00:00.274858
> >
> >Nothing to worry about, unfortunately we do have some time-sensitive
> >tests so if the tester does not receive enough timeslots it may end
> >up interrupting later than expected.
> >
> >I'd love to fix these but hadn't found a way to obtain CPU time
> >of a postgresql session.
>
> Can't you do something like, get the pid of the backend process and then use
> a system call to get the cpu time maybe using via /proc/[PID]/stat on linux
>
> and maybe something like this on Windows:
> https://msdn.microsoft.com/en-us/library/windows/desktop/ms683223(v=vs.85).aspx

It would mean using a completely different framework for those tests,
right now we use the .sql and _expect pair as all the rest...

Or, we would need to expose an internal SQL function for this specific
purpose.

--strk;
_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|

Re: Postgis 2.3.1 regression test failure on NetBSD-7 amd64

Greg Troxel-2
In reply to this post by Stephen Woodbridge
Stephen Woodbridge <[hidden email]> writes:

> On 12/5/2016 12:21 PM, Sandro Santilli wrote:
>> On Mon, Dec 05, 2016 at 10:06:42AM -0500, Greg Troxel wrote:
>>
>>> -contains interrupted on time
>>> +contains interrupted late: 00:00:00.274858
>>
>> Nothing to worry about, unfortunately we do have some time-sensitive
>> tests so if the tester does not receive enough timeslots it may end
>> up interrupting later than expected.
>>
>> I'd love to fix these but hadn't found a way to obtain CPU time
>> of a postgresql session.
>
> Can't you do something like, get the pid of the backend process and
> then use a system call to get the cpu time maybe using via
> /proc/[PID]/stat on linux
>
> and maybe something like this on Windows:
> https://msdn.microsoft.com/en-us/library/windows/desktop/ms683223(v=vs.85).aspx

And then others methods for a big list of other operating systems.  This
seems unportable enough that it's probably best not to go there.
_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel
Reply | Threaded
Open this post in threaded view
|

Re: Postgis 2.3.1 regression test failure on NetBSD-7 amd64

Greg Troxel-2
In reply to this post by Sandro Santilli-4

Sandro Santilli <[hidden email]> writes:

> On Mon, Dec 05, 2016 at 10:06:42AM -0500, Greg Troxel wrote:
>
>> -contains interrupted on time
>> +contains interrupted late: 00:00:00.274858
>
> Nothing to worry about, unfortunately we do have some time-sensitive
> tests so if the tester does not receive enough timeslots it may end
> up interrupting later than expected.
>
> I'd love to fix these but hadn't found a way to obtain CPU time
> of a postgresql session.

Thanks.  My real worry was if there was a bug lurking.   I ran it again
without the -j8 compile (on a 4-core machine) going, and didn't get an
error.

_______________________________________________
postgis-devel mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/postgis-devel