pgspot
pgspot copied to clipboard
timescale
Spot vulnerabilities in postgres SQL scripts
How can I resolve these warnings? ```sql WITH s AS ( SELECT "id" FROM public.task AS t LEFT JOIN "pg_catalog"."pg_locks" AS l ON "locktype" OPERATOR(pg_catalog.=) 'userlock' AND "mode" OPERATOR(pg_catalog.=) 'AccessExclusiveLock'...
Since we don't do control flow analysis our object creation tracking can mask potential problems and produce false negatives. The following snippet would not produce a warning about unsafe function...
In the current version of `pgspot`, only the number of statements with the states _error_, _warning_, and _unknown_ are counted and shown. It might be helpful for the user to...
Postgres' guidelines on `SECURITY DEFINER` functions mention that it's desirable to revoke `EXECUTE` from `PUBLIC` from them: https://www.postgresql.org/docs/current/sql-createfunction.html#SQL-CREATEFUNCTION-SECURITY
