Skip to content

Improve experience when pljava.module_path is incorrect #350

Description

@jcflack

The module path must include both the pljava (implementation) and pljava-api jars. The automatic construction of the default value suffices when they are in the expected installed location, but the experience could be better when the path is wrong.

When the implementation jar can't be found, that manifests as the familiar failure to load the Backend class, for which there's already a suitable ereport. However, the nice message is followed by a segfault, an unintended consequence of bbbb75c. That should be fixed.

When the implementation jar is found but the API jar (on which it depends) is not, the experience is not good. The Java VM dashes off a note to standard error standard output!:

Error occurred during initialization of boot layer
java.lang.module.FindException: Module org.postgresql.pljava not found

and summarily does a process exit. The message to standard error should end up in the log if logging_collector is active, but otherwise goes wherever the backend's standard error output! goes, and may will probably never be seen.

Ideally, there will be some way to improve that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions