Re: PL/Java 1.5.1_BETA2

Re: Chapman Flack 2018-09-16 <5B9ECCD1(dot)1050309(at)anastigmatix(dot)net>
> > i.e. it's replacing both occurrences of "i386" by "1".
>
> Ok, that's irritating. I can guess what is happening. I implement the
> -Dpljava.libjvmdefault by passing the string into cpp with a -D, and that
> gets converted to a string using the CppAsString2 macro, and that apparently
> is not protected from expansion of other macros, and I bet something is
> defining i386 to be 1.
>
> Phooey.
>
> I don't know if that will be easy to fix using cpp. An alternative would be
> to pass it to cpp already quoted according to C rules, but that would be
> somewhat ugly to express in a Maven build script.

We could try "-Ui386" if there's a way to pass that flag into the
build process?

Filed at https://github.com/tada/pljava/issues/176, let's continue
there.

> Your SET command to correct the library name completed the installation
> of PL/Java, but at that point it was no longer within a CREATE EXTENSION
> command, so the various functions, tables, etc., have just been installed
> 'loose' (exactly as they would if you were installing in 9.0 or earlier
> with no 'extension' mechanism).

Oh, that's unexpected. Wouldn't it be time to unsupport that and move
to a "normal" extension .sql script?

> > Proceeding to load the examples:
>
> > Server beendete die Verbindung unerwartet
>
> Is there anything in the server log with details of the crash?
> In many cases there will be a lengthy message from the JVM in the server
> log, and that message will contain a file name (something like
> /tmp/hs_err_pidnnnn.log) which will contain *even more* detail.
> I would be interested to see that. Was this still on i386 ?

Filed as https://github.com/tada/pljava/issues/177 with attachment.

> > 20:07:07 ERROR: java.lang.ClassNotFoundException: org.postgresql.pljava.example.annotation.ComplexTuple
> > 20:07:07 CONTEXT: SQL statement "SELECT javatest.assertHasValues( CAST('(1,2)' AS javatest.complextuple), 1, 2)"
>
> I believe you'll find this a Heisenbug, and it will go away if you repeat
> the build and the test.

https://github.com/tada/pljava/issues/178

Christoph