Skip to content

Postgres database migration failed : permission denied for schema public #756

@jgarec

Description

@jgarec

Hello,

We have a critical issue when trying to upgrade from 9.4.0 to latest version.

We are using postgres to persist data and we use a dedicated schema.
We are in a situation where we are not allowed to deploy objects in "public" schema.

Is there any reason why you choose to deploy this materialized view (org_libyears_mv) into public instead of the default schema for the current user ?

I think script 0016 won't work in our case "public" is used for reason_enum whereas it was deployed in another schema

Regards,
Jérôme

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