Skip to content

Commit a4a95a5

Browse files
committed
Update release notes
1 parent edee802 commit a4a95a5

File tree

1 file changed

+53
-6
lines changed

1 file changed

+53
-6
lines changed

src/site/markdown/releasenotes.md.vm

Lines changed: 53 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,19 +10,52 @@
1010
#set($ghbug = 'https://github.com/tada/pljava/issues/')
1111
#set($ghpull = 'https://github.com/tada/pljava/pull/')
1212

13-
$h2 PL/Java 1.5.7
13+
$h2 PL/Java 1.5.8
1414

15-
1.5.7 is a bug-fix release, with a single issue backpatched from the 1.6
16-
branch, correcting a problem in XML Schema validation in some non-`en_US`
17-
locales.
15+
1.5.8 adds support for PostgreSQL 14, fixes two bugs, and begins preparation
16+
for the impact of changes to Java's permission enforcement coming in Java 17
17+
and later with JEP 411.
18+
19+
$h3 PL/Java with Java 17 and later: JEP 411
20+
21+
Current versions of PL/Java rely on Java security features that will be affected
22+
by JEP 411, beginning with Java 17. Java 17 itself will continue to provide the
23+
needed capabilities, with only deprecation marks and warnings added. Java 17 is
24+
also positioned as a long-term support release, so the option of continuing to
25+
run a current (1.5.8 or latest 1.6) PL/Java release without loss of function
26+
will be available, if needed, by continuing to run with Java 17.
27+
28+
The PL/Java 1.5 series has had a good run, and is not expected to receive
29+
backports of future, post-JEP 411 functionality.
30+
31+
For more on how PL/Java will adapt, please read about [JEP 411][jep411] on
32+
the PL/Java wiki.
1833

1934
$h3 Bugs fixed
2035

21-
* [XML Schema regression-test failure in de_DE locale](${ghbug}312)
36+
* [MalformedInputException: Input length = 1 in 1.5](${ghbug}340)
37+
38+
The bug was exercised in a database where `server_encoding` was `SQL_ASCII`.
39+
The more-principled treatment of `SQL_ASCII` in PL/Java 1.6 has been
40+
backported, and is described [here][sqlascii].
41+
42+
* [Crash in autovacuum if a PL/Java functional index exists](${ghbug}355)
43+
44+
Functional indexes over PL/Java functions can now be autovacuumed
45+
in PG 9.5 or later. In earlier versions, a `feature_not_supported` error
46+
will be reported instead of crashing. That can be avoided by setting the
47+
`autovacuum_enabled` storage parameter to `false` on any table having
48+
a Java-based functional index, and running explicit `VACUUM` periodically
49+
on such tables. Prior to PG 8.4, there was no such per-table setting, and
50+
the only workaround would be to forego autovacuum database-wide and use
51+
explicit `VACUUM` on some schedule.
52+
53+
[jep411]: https://github.com/tada/pljava/wiki/JEP-411
54+
[sqlascii]: use/charsets.html#The_special_encoding_SQL_ASCII
2255

2356
$h3 Credits
2457

25-
Thanks to Christoph Berg for the report.
58+
Thanks to `yazun` and `ricdhen` for reporting the bugs fixed in this release.
2659

2760
$h2 Earlier releases
2861

@@ -35,6 +68,20 @@ $h2 Earlier releases
3568
#set($h4 = '#####')
3669
#set($h5 = '######')
3770

71+
$h2 PL/Java 1.5.7 (16 November 2020)
72+
73+
1.5.7 is a bug-fix release, with a single issue backpatched from the 1.6
74+
branch, correcting a problem in XML Schema validation in some non-`en_US`
75+
locales.
76+
77+
$h3 Bugs fixed
78+
79+
* [XML Schema regression-test failure in de_DE locale](${ghbug}312)
80+
81+
$h3 Credits
82+
83+
Thanks to Christoph Berg for the report.
84+
3885
$h2 PL/Java 1.5.6 (4 October 2020)
3986

4087
This release adds support for PostgreSQL 13.

0 commit comments

Comments
 (0)