Subject: Re: [Pljava-dev] Draft release notes in preparation for 1.5.1-BETA1 References: <5947FF8B.9040803@anastigmatix.net> <7a9451ce-eed8-ddec-4fff-add3cfb351f9@matrix.gatewaynet.com> <5949120C.2080705@anastigmatix.net> <5949198B.3080304@anastigmatix.net> <87160f24-02f5-60cd-27df-aca8d3de1be8@matrix.gatewaynet.com> From: Chapman Flack Message-ID: Date: Tue, 20 Jun 2017 09:35:00 -0400 MIME-Version: 1.0 In-Reply-To: <87160f24-02f5-60cd-27df-aca8d3de1be8@matrix.gatewaynet.com> Content-Type: text/plain; charset=utf-8 On 06/20/2017 09:08 AM, Achilleas Mantzios wrote: > Thanx for the update. So what do you recommend for our case? By the time > we move to 10 (might be one year from now), just try to re-install the > corresponding latest stable version of pl/java? I would recommend going to PL/Java 1.5.1 once it reaches full (not beta) release, irrespective of when you plan to upgrade PostgreSQL. Then you'll be running the latest official release, and when you do later upgrade PostgreSQL, PL/Java will need no extra attention. (As a bonus, PL/Java 1.5.1 plays well with pg_upgrade, so you can binary-upgrade the cluster when the time comes.) Moving to 1.5.1 from 1.6.0-SNAPSHOT might look like a 'downgrade', but should be fairly straightforward to do, as the 1.6.0-SNAPSHOT line has not made any incompatible schema changes (yet). Did you install with CREATE EXTENSION, or a plain LOAD? -Chap