Skip to content

Installed by LOAD then packaged as extension broken since postgres/postgres@b9b21ac #434

Closed

Description

@jcflack

PL/Java still supports a legacy non-extension loading method, just using LOAD. It can still be useful in odd cases, such as when a DBA doesn't have write access to the canonical extension directory.

Support has also been retained for gathering such a 'freestanding' installation into an extension later: PostgreSQL dropped the one-step CREATE EXTENSION foo FROM unpackaged for that, but PL/Java still understands a three-step

CREATE EXTENSION pljava VERSION unpackaged;
\c
ALTER EXTENSION pljava UPDATE;

to do the same thing. But postgres/postgres@b9b21ac has thrown a wrench in the way that currently works. The symptom will be a maddeningly vague An attempt was made to call a PostgreSQL backend function after an elog(ERROR) had been issued (and you don't see the elog(ERROR) that's responsible, because PostgreSQL severely suppresses messages during extension processing).

It is probably little-enough used that it needn't be a hot item to fix, but the CI scripts should stop trying to test it, until it is fixed.

Activity

  1. jcflack commented on Jun 13, 2023

    @jcflack
    ContributorAuthor

    Believed resolved in 1.6.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions