pg.ddx.io pgsql-pkg-debian@postgresql.org mailing list archive
help / color / mirror / Atom feedPL/Java 1.5.1
8+ messages / 3 participants
[nested] [flat]
* PL/Java 1.5.1
@ 2018-10-16 02:38 Chapman Flack <chap@anastigmatix.net>
2018-10-16 03:32 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-16 11:32 ` Re: PL/Java 1.5.1 Christoph Berg <myon@debian.org>
0 siblings, 2 replies; 8+ messages in thread
From: Chapman Flack @ 2018-10-16 02:38 UTC (permalink / raw)
To: Christoph Berg <myon@debian.org>; pgsql-pkg-debian
I expect to shortly tag a 1.5.1 release (just in time to say it builds
with PG 11).
I had a few last-minute thoughts about the .deb builds (in order of
outlandishness, maybe).
1. It looks as if they are being built with libjvmdefault => java 8.
Do some of the distro releases they are being built for have a later
version of Java as the default? (If I'm looking in the right places,
it seems that the Ubuntu default-jdk-headless is 8 for xenial and
artful, 10 for bionic, 11 for cosmic. Debian's default-jdk seems to
be 7 in wheezy and jessie, 8 in stretch, 10 in buster and sid,
11 in experimental).
It might be nice to build pljava packages where libjvmdefault => the
default version for the release. It still has to be /built/ with 8, but
can then run with the later versions on releases that have them. The
user can always set pljava.libjvm_location to a different version, but
this would have the property that leaving it alone means getting the
expected Java version, and (in recent releases) having access to newer
Java features, without having to take extra steps.
2. You seem to be building packages for PG from 11 back to 9.3. For that
range of PG versions, it would be possible to add the -Psaxon-examples
option on the build command (if you can stomach having the 5 MB
Saxon-HE-9.8.0.14.jar as a build dependency). The jar can be left out
of the package as an optional runtime dependency. The Saxon examples
would just be included in the pljava-examples jar, they would get
automatically loaded in PG if the user installs the jar. They wouldn't
work unless the user also installed the Saxon-HE jar, but that would be
the only step needed for someone who might want to try them.
It's actually safe to add -Psaxon-examples when building for any PG
version back to 8.4. Before 8.4, those examples can't be included
in pljava-examples.jar because their deployment SQL commands would
be syntax errors and prevent installing the jar, which is why I made
the build option.
3. Here is the possibly outlandish thought: I see in
pool/main/p/postgresql-pljava/ that there are existing .debs in there
for PG 9.2 back to 8.1, and they are based on really ancient PL/Java
versions with serious known bugs. I have been taking pains to make sure
PL/Java 1.5.x stays buildable back to 8.2 (but not 8.1, sadly). It would
be great if there could be packages in the repo so that those old buggy
ones would not be the only ones available. I understand that your build
arrangements probably don't even have those six PG versions present to
build against, and there is probably no justification for doing ongoing,
automated builds for them. Even if it were possible to just do one round
of builds and leave them there (as it appears those old packages are
simply left in the directory from years ago), that would benefit anyone
who needs, for some reason, to use such an old PG version.
Someone has actually opened a PL/Java issue this week who is using
PG 8.3. :) I did not press for details about why.... That's on Windows
though.
Cheers,
-Chap
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PL/Java 1.5.1
2018-10-16 02:38 PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
@ 2018-10-16 03:32 ` Chapman Flack <chap@anastigmatix.net>
2018-10-16 14:16 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
1 sibling, 1 reply; 8+ messages in thread
From: Chapman Flack @ 2018-10-16 03:32 UTC (permalink / raw)
To: Christoph Berg <myon@debian.org>; pgsql-pkg-debian
On 10/15/18 22:38, Chapman Flack wrote:
> artful, 10 for bionic, 11 for cosmic. Debian's default-jdk seems to
> be 7 in wheezy and jessie, 8 in stretch, 10 in buster and sid,
> 11 in experimental).
>
> It might be nice to build pljava packages where libjvmdefault => the
> default version for the release. It still has to be /built/ with 8, but
... except in this scheme, it would have to be built with 7 for wheezy or
jessie (the build JDK can't be /newer/ than the runtime). Slipped my mind.
-Chap
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PL/Java 1.5.1
2018-10-16 02:38 PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-16 03:32 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
@ 2018-10-16 14:16 ` Chapman Flack <chap@anastigmatix.net>
2018-10-16 16:11 ` Re: PL/Java 1.5.1 Christoph Berg <cb@df7cb.de>
0 siblings, 1 reply; 8+ messages in thread
From: Chapman Flack @ 2018-10-16 14:16 UTC (permalink / raw)
To: Christoph Berg <myon@debian.org>; pgsql-pkg-debian
On 10/15/2018 11:32 PM, Chapman Flack wrote:
> On 10/15/18 22:38, Chapman Flack wrote:
>> artful, 10 for bionic, 11 for cosmic. Debian's default-jdk seems to
>> be 7 in wheezy and jessie, 8 in stretch, 10 in buster and sid,
>> 11 in experimental).
>>
>> It might be nice to build pljava packages where libjvmdefault => the
>> default version for the release. It still has to be /built/ with 8, but
>
> ... except in this scheme, it would have to be built with 7 for wheezy or
> jessie (the build JDK can't be /newer/ than the runtime). Slipped my mind.
Hmm, it also slipped my mind that the pom.xml contains
<target>1.6</target>, so it should be ok to build with 8 everywhere,
the built classes should still work in Java 6/7. I don't think
I've confirmed that recently, but I can check easily enough later today.
-Chap
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PL/Java 1.5.1
2018-10-16 02:38 PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-16 03:32 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-16 14:16 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
@ 2018-10-16 16:11 ` Christoph Berg <cb@df7cb.de>
0 siblings, 0 replies; 8+ messages in thread
From: Christoph Berg @ 2018-10-16 16:11 UTC (permalink / raw)
To: pgsql-pkg-debian@lists.postgresql.org,Chapman Flack <chap@anastigmatix.net>; Christoph Berg <myon@debian.org>; pgsql-pkg-debian
Jessie doesn't have Java 8, so that question does not matter for packaging.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PL/Java 1.5.1
2018-10-16 02:38 PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
@ 2018-10-16 11:32 ` Christoph Berg <myon@debian.org>
2018-10-16 12:49 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
1 sibling, 1 reply; 8+ messages in thread
From: Christoph Berg @ 2018-10-16 11:32 UTC (permalink / raw)
To: Chapman Flack <chap@anastigmatix.net>; +Cc: pgsql-pkg-debian
Re: Chapman Flack 2018-10-16 <5BC54F32.7020705@anastigmatix.net>
> 1. It looks as if they are being built with libjvmdefault => java 8.
> Do some of the distro releases they are being built for have a later
> version of Java as the default? (If I'm looking in the right places,
> it seems that the Ubuntu default-jdk-headless is 8 for xenial and
> artful, 10 for bionic, 11 for cosmic. Debian's default-jdk seems to
> be 7 in wheezy and jessie, 8 in stretch, 10 in buster and sid,
> 11 in experimental).
Seems about right.
> It might be nice to build pljava packages where libjvmdefault => the
> default version for the release. It still has to be /built/ with 8, but
> can then run with the later versions on releases that have them. The
> user can always set pljava.libjvm_location to a different version, but
> this would have the property that leaving it alone means getting the
> expected Java version, and (in recent releases) having access to newer
> Java features, without having to take extra steps.
Currently pljava.libjvm_location is set to the jvm version the package
was built with. The .deb will have this dependency:
Depends: ${jre:Depends} | default-jre-headless
The first problem here is that this is missing "| java-runtime-headless"
to allow arbitrary jre versions.
What we probably should to is to change this to
Depends: default-jre-headless | ${jre:Depends} | java-runtime-headless
Apt doesn't consistently pick the first alternative, but there's rule
that the preferred one should come first.
... and also point pljava.libjvm_location at the default version.
> 2. You seem to be building packages for PG from 11 back to 9.3. For that
> range of PG versions, it would be possible to add the -Psaxon-examples
> option on the build command (if you can stomach having the 5 MB
> Saxon-HE-9.8.0.14.jar as a build dependency). The jar can be left out
> of the package as an optional runtime dependency. The Saxon examples
> would just be included in the pljava-examples jar, they would get
> automatically loaded in PG if the user installs the jar. They wouldn't
> work unless the user also installed the Saxon-HE jar, but that would be
> the only step needed for someone who might want to try them.
>
> It's actually safe to add -Psaxon-examples when building for any PG
> version back to 8.4. Before 8.4, those examples can't be included
> in pljava-examples.jar because their deployment SQL commands would
> be syntax errors and prevent installing the jar, which is why I made
> the build option.
I'm not really following how that relates to the range of PG versions?
Because it's "only" 8.4+ ?
> 3. Here is the possibly outlandish thought: I see in
> pool/main/p/postgresql-pljava/ that there are existing .debs in there
> for PG 9.2 back to 8.1, and they are based on really ancient PL/Java
> versions with serious known bugs. I have been taking pains to make sure
> PL/Java 1.5.x stays buildable back to 8.2 (but not 8.1, sadly). It would
> be great if there could be packages in the repo so that those old buggy
> ones would not be the only ones available. I understand that your build
> arrangements probably don't even have those six PG versions present to
> build against, and there is probably no justification for doing ongoing,
> automated builds for them. Even if it were possible to just do one round
> of builds and leave them there (as it appears those old packages are
> simply left in the directory from years ago), that would benefit anyone
> who needs, for some reason, to use such an old PG version.
Some of the very old packages were not built on/for apt.pg.o but
copied over from Debian. The oldest PG version we have is 8.2, which
I'm still keeping alive, but in sid-pgdg only. The other distributions
have what was supported while they were alive, so the window of
package versions updated shifted over time.
We are usually not updating modules for PG versions that aren't
supported anymore, just to cut the maintenance down, but we could
probably give the older PG versions a one-time try. (This wouldn't
extend to unsupported distributions, though - the build chroots are
gone.)
> Someone has actually opened a PL/Java issue this week who is using
> PG 8.3. :) I did not press for details about why.... That's on Windows
> though.
... that doesn't make it any better :P
Christoph
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PL/Java 1.5.1
2018-10-16 02:38 PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-16 11:32 ` Re: PL/Java 1.5.1 Christoph Berg <myon@debian.org>
@ 2018-10-16 12:49 ` Chapman Flack <chap@anastigmatix.net>
2018-10-19 01:00 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
0 siblings, 1 reply; 8+ messages in thread
From: Chapman Flack @ 2018-10-16 12:49 UTC (permalink / raw)
To: Christoph Berg <myon@debian.org>; pgsql-pkg-debian
On 10/16/18 07:32, Christoph Berg wrote:
>> 2. You seem to be building packages for PG from 11 back to 9.3. For that
>> range of PG versions, it would be possible to add the -Psaxon-examples
...
>> It's actually safe to add -Psaxon-examples when building for any PG
>> version back to 8.4. Before 8.4, those examples can't be included
> I'm not really following how that relates to the range of PG versions?
> Because it's "only" 8.4+ ?
The saxon-examples functions are declared with SQL syntax that didn't
exist pre-8.4, so they would just be rejected as syntax errors in 8.3
or 8.2.
The documentation illustrating how to call them uses named-parameter
notation with => so it works as far back as 9.5, and with a simple
substitution of := for => they can be called the same way as far back
as 9.0. But the illustrations also show FROM clauses with LATERAL or
with a function referring to earlier entries, which is only possible
in 9.3+.
So the saxon-examples PG version range dependency boils down to:
* the functions can be built and installed in any version 8.4 and up
* they are easy to use in 9.5 and up, following exactly the illustrations
in the docs
* they are almost as easy to use in 9.3 and 9.4, changing => to :=
* from 9.2 back to 8.4, they work, but require increasing devilish
cleverness to write SQL queries that use them.
-Chap
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PL/Java 1.5.1
2018-10-16 02:38 PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-16 11:32 ` Re: PL/Java 1.5.1 Christoph Berg <myon@debian.org>
2018-10-16 12:49 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
@ 2018-10-19 01:00 ` Chapman Flack <chap@anastigmatix.net>
2018-10-19 10:07 ` Re: PL/Java 1.5.1 Christoph Berg <myon@debian.org>
0 siblings, 1 reply; 8+ messages in thread
From: Chapman Flack @ 2018-10-19 01:00 UTC (permalink / raw)
To: Christoph Berg <myon@debian.org>; pgsql-pkg-debian
Hi Christoph,
Was there some objection in principle (or maybe just download size) to
building with -Psaxon-examples ?
If it is not objectionable, my preference would be to build with that
option (whenever the PG version >= 8.4 anyway).
A lot of the examples are just toy learning aids or tests, but the Saxon
examples are there for a useful, non-trivial purpose: to give real SQL:2006+
XML Query functionality, which core PG still lacks.
So I would like to make it as easy as possible for the user to try out
those examples. Even leaving the Saxon library as an optional download,
so one extra thing would have to be downloaded before those examples
work, that would still be less fuss than having to build the example
code separately AND download the library.
What do you think?
Thanks,
-Chap
On 10/16/18 08:49, Chapman Flack wrote:
> On 10/16/18 07:32, Christoph Berg wrote:
>
>>> 2. You seem to be building packages for PG from 11 back to 9.3. For that
>>> range of PG versions, it would be possible to add the -Psaxon-examples
> ...
>>> It's actually safe to add -Psaxon-examples when building for any PG
>>> version back to 8.4. Before 8.4, those examples can't be included
>
>> I'm not really following how that relates to the range of PG versions?
>> Because it's "only" 8.4+ ?
>
> The saxon-examples functions are declared with SQL syntax that didn't
> exist pre-8.4, so they would just be rejected as syntax errors in 8.3
> or 8.2.
>
> The documentation illustrating how to call them uses named-parameter
> notation with => so it works as far back as 9.5, and with a simple
> substitution of := for => they can be called the same way as far back
> as 9.0. But the illustrations also show FROM clauses with LATERAL or
> with a function referring to earlier entries, which is only possible
> in 9.3+.
>
> So the saxon-examples PG version range dependency boils down to:
>
> * the functions can be built and installed in any version 8.4 and up
> * they are easy to use in 9.5 and up, following exactly the illustrations
> in the docs
> * they are almost as easy to use in 9.3 and 9.4, changing => to :=
> * from 9.2 back to 8.4, they work, but require increasing devilish
> cleverness to write SQL queries that use them.
>
> -Chap
>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PL/Java 1.5.1
2018-10-16 02:38 PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-16 11:32 ` Re: PL/Java 1.5.1 Christoph Berg <myon@debian.org>
2018-10-16 12:49 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-19 01:00 ` Re: PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
@ 2018-10-19 10:07 ` Christoph Berg <myon@debian.org>
0 siblings, 0 replies; 8+ messages in thread
From: Christoph Berg @ 2018-10-19 10:07 UTC (permalink / raw)
To: Chapman Flack <chap@anastigmatix.net>; +Cc: pgsql-pkg-debian
Re: Chapman Flack 2018-10-19 <5BC92CB0.2020007@anastigmatix.net>
> Was there some objection in principle (or maybe just download size) to
> building with -Psaxon-examples ?
I'm just lacking time atm, I filed your last mail as
https://salsa.debian.org/postgresql/postgresql-pljava/issues/1
so it doesn't get lost completely.
> If it is not objectionable, my preference would be to build with that
> option (whenever the PG version >= 8.4 anyway).
>
> A lot of the examples are just toy learning aids or tests, but the Saxon
> examples are there for a useful, non-trivial purpose: to give real SQL:2006+
> XML Query functionality, which core PG still lacks.
>
> So I would like to make it as easy as possible for the user to try out
> those examples. Even leaving the Saxon library as an optional download,
> so one extra thing would have to be downloaded before those examples
> work, that would still be less fuss than having to build the example
> code separately AND download the library.
>
> What do you think?
It makes a lot of sense. If I should forget, could you ping me again
once the whole upload-everything-for-PG11 dust has settled in a few
weeks?
Christoph
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2018-10-19 10:07 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-10-16 02:38 PL/Java 1.5.1 Chapman Flack <chap@anastigmatix.net>
2018-10-16 03:32 ` Chapman Flack <chap@anastigmatix.net>
2018-10-16 14:16 ` Chapman Flack <chap@anastigmatix.net>
2018-10-16 16:11 ` Christoph Berg <cb@df7cb.de>
2018-10-16 11:32 ` Christoph Berg <myon@debian.org>
2018-10-16 12:49 ` Chapman Flack <chap@anastigmatix.net>
2018-10-19 01:00 ` Chapman Flack <chap@anastigmatix.net>
2018-10-19 10:07 ` Christoph Berg <myon@debian.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox