crunchy_check_access icon indicating copy to clipboard operation
crunchy_check_access copied to clipboard

Functions and views to facilitate PostgreSQL object access inspection

Results 6 crunchy_check_access issues
Sort by recently updated
recently updated
newest added

Replace uses of pg_authid with pg_roles so it can be used in Postgres instances where privileged catalog tables are restricted, such as public cloud providers (AWS)

Following the examples in your blog article https://info.crunchydata.com/blog/postgresql-defaults-and-impact-on-security-part-1, `all_access()` seems to return incomplete results: joe is a member of both dbadm and endusers, so his privileges should be the same...

The current goal and function of check_access is to report on actual access routes. This is useful to report what roles can actively perform actions on tables. This PR adds...

Casting from oidvector to text produced a list of OIDs that seemed less helpful to the reader than what `pg_catalog.pg_get_function_arguments` produces, so use that.

Adding of "@extschema@" for SQL objects in order. Currently, if extension is installed in an another schema of public, we need to set search_path in order to make it working...

Incorporate all recent PRs into a new version release Add CHANGELOG & LICENSE files Add precommit hooks

enhancement