This release includes small bug fixes. The following issues have been
resolved:
* Some incorrect escaping in shp2pgsql
* 3D computation in length_spheroid
* Multiple schema support improved
* Better join selectivity estimates
* Improved postgis_restore.pl script
PR: ports/81501
Submitted by: maintainer
* fix patch-src::jrd::gds.cpp
* use "libdata/firebird" for *.msg
* install all *.msg files (not only firebird.msg)
* fix pkg-plist
* use more strict permissions
* use INSTALL_DATA instead of INSTALL_PROGRAM to install shared libs and similar files
* clean Makefile
* update RELNOTES
PR: ports/81363
Submitted by: skv
Approved by: maintainer
- Fix problem with firebird.msg. It was installed only for -server,
but it's necessary for -client too (thanks to skv@ for pointing this out).
- Utilize PORTDOCS and SUBFILES, respect NOPORTDOCS.
- Utilize DOCSDIR and EXAMPLESDIR.
- Back to use do-build.
- Add $FreeBSD$ tag to pkg-plist* and pkg-install.
- Remove code that changes automatically /etc/services and /etc/inetd.conf and
change pkg-message to reflect this.
PR: ports/81214
Submitted by: maintainer
installed, the patched gram.y file would not be used and the security
patch would be a no-op. Also, I've had reports of compilation errors
related to bison.
Since checking for the correct version of bison is hard and error
prone, I'm doing what the postgresql distribution does - patching the
yacc:ed .c file to get rid of the building dependency.
Bumping portrevision of -server.
Pointy hat to: me
Noticed by: Mike Harding and others
Security: http://www.vuxml.org/freebsd/6b4b0b3f-8127-11d9-a9e7-0001020eed82.html
Approved by: seanc (implicit)
please see the HISTORY file included in the Release, but a summary
consists of:
* Change encoding function signature to prevent misuse
* Change "contrib/tsearch2" to avoid unsafe use of INTERNAL function
results
* Repair race condition between relation extension and VACUUM
This could theoretically have caused loss of a page's worth of
freshly-inserted data, although the scenario seems of very low
probability. There are no known cases of it having caused more than
an Assert failure.
Security: http://www.postgresql.org/about/news.315
