Skip to content

Emit warning when adding pg_catalog on db-schemas #4359

@steve-chavez

Description

@steve-chavez

Oh.. That explains it. What was the rationale for this decision?

We did it that way to avoid exposing sensitive information, and all roles have implicit access to information_schema and pg_catalog, IIRC revoking SELECT privileges to those schemas can break postgres in unexepected ways.

Additionally it would be nice to get a warning when it is explicitly added to db-schemas instead of silently ignoring it.

Great idea. We should do that and also document this decision.

Originally posted by @steve-chavez in #4252 (reply in thread)

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsOnly related to documentationmessagesuser-facing error/informative messages

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions