Skip to content

Move third-party extensions from public schema to extensions #257

@erichanson

Description

@erichanson

This seems to be an emerging trend, and a reasonable one given PostgreSQL extensions' architectural flaws. It's impossible to do the "right" thing here since every extension can only be installed once, and they have to be installed into a particular schema, so if two different projects need to coexist but look for an extension in different places, boom. Until we just stop using extensions entirely, write code that looks for them in the extensions schema.

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