plpgsql_check
pgaudit
Our great sponsors
plpgsql_check | pgaudit | |
---|---|---|
3 | 5 | |
605 | 1,183 | |
- | 3.0% | |
8.2 | 5.0 | |
about 1 month ago | 21 days ago | |
C | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
plpgsql_check
-
Supabase Local Dev: migrations, branching, and observability
Finally, while you wait for us to make progress on the Language Server, we’ve added support for linting through the excellent plpgsql_check extension.
- Postgres Invalid objects
- PostGIS – Spatial and Geographic Objects for PostgreSQL
pgaudit
-
Show HN: I built this Postgres logger for you guys to check out
I think pgAudit it still the best and it's not a major issue. You can try my PR that fixes this issue https://github.com/pgaudit/pgaudit/pull/219 it should work and it should handle the other types of SELECT's that need update permissions but are not actually updating anything https://pglocks.org/?pglock=RowShareLock
- PgAudit: Open-Source PostgreSQL Audit Logging
- Auditing CREATE/DROP DATABASE
-
How Postgres Audit Tables Saved Us from Taking Down Production
You can use pgaudit, it's an extension that let's you audit DDL/DML statements. It's a great auditing mechanism. I use it on all our prod postgres instances, but have only "DML" enabled, because of the potential performance overhead
https://github.com/pgaudit/pgaudit
-
Auditing PostgreSQL Using pgAudit
pgAudit, with all its capabilities, simplifies the process of auditing by generating the audit trail log. Though there are a few caveats, like logging of renamed objects under the same name, it is still a robust tool that provides the required functionality. However, the audit information written in logs may not be just ideal for the auditing process - the auditing process is even better when those logs can be converted to a database schema, and audit data can be loaded to the database so you can easily query the information. This is where the PostgreSQL Audit Log Analyzer (pgAudit Analyze) is helpful. For more information, refer to the github pages of pgAudit and pgAudit Analyze.
What are some alternatives?
pgsentinel - postgresql extension providing Active session history
pgaudit_analyze - PostgreSQL Audit Analyzer
pg_show_plans - Show query plans of all currently running SQL statements
psycopg2 - PostgreSQL database adapter for the Python programming language
orafce - The "orafce" project implements in Postgres some of the functions from the Oracle database that are missing (or behaving differently).Those functions were verified on Oracle 10g, and the module is useful for production work.
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
docker-postgis - Docker image for PostGIS
temporal_tables - Temporal Tables PostgreSQL Extension
tds_fdw - A PostgreSQL foreign data wrapper to connect to TDS databases (Sybase and Microsoft SQL Server)
sqlite-wf - Simple visual ETL tool
pg_plan_guarantee - Postgres Query Optimizer Extension that guarantees your desired plan will not change