This PR is about calling the pg_catalog schema explicitly to protect the Database's Search Path as suggested by PostgreSQL documentation:
If you write your queries with specific schema.object form, including objects that exist in the pg_catalog (e.g. calling SELECT pg_catalog.lower('ALICE');), then you are not immediately vulnerable to this issue.
This PR is about calling the
pg_catalog
schema explicitly to protect the Database's Search Path as suggested by PostgreSQL documentation: