database-optimizer

Fail

Audited by Runlayer on Mar 7, 2026

Risk Level: HIGH
Scan Summary
Max Score
90%
Files
6
Flagged
3
Chunks
10
Flagged Files (3)
database-optimizer/references/postgresql-tuning.mdHIGH
90.1%

Risky tool definition detected

LIMIT 1000; RESET work_mem; ``` ### Maintenance Work Memory ```sql -- For VACUUM, CREATE INDEX, ALTER TABLE -- Recommended: 1-2GB for production systems ALTER SYSTEM SET maintenance_work_mem = '2GB'; -- Autovacuum workers use proportional amount ALTER SYSTEM SET autovacuum_work_mem = '512MB'; ``` ### Effective Cache Size ```sql -- Planner hint for available OS cache -- Recommended: 50-75% of total RAM -- For 16GB RAM: ALTER SYSTEM SET effective_cache_size = '12GB'; ``` ## Query Planner Settings

database-optimizer/references/monitoring-analysis.mdMEDIUM
89.4%

Risky tool definition detected

database-optimizer/references/mysql-tuning.mdMEDIUM
89.0%

Risky tool definition detected

Description: VALUES IN ('cancelled', 'refunded') ); ``` ## Replication Optimization ### Binary Log Settings ```sql -- Binary log format SET GLOBAL binlog_format = 'ROW'; -- ROW, STATEMENT, or MIXED -- Binary log cache size SET GLOBAL binlog_cache_size = 1048576; -- 1MB per transaction -- Sync binary log (durability vs performance) SET GLOBAL sync_binlog = 1; -- Safest, sync after each commit -- sync_binlog = 0 -- Fastest, let OS handle flushing -- Expire binary logs after N days SET GLOBAL binlo

Passed Files (3)Click to expand
database-optimizer/references/query-optimization.mdOK
49.4%

Tool passed security scan

database-optimizer/references/index-strategies.mdOK
42.9%

Tool passed security scan

database-optimizer/SKILL.mdOK
37.0%

Tool passed security scan

Audit Metadata
Max File Score
90%
Classification
KNOWN_SERVER_ALL_UNKNOWN
Files Scanned
6
Files Flagged
3
Chunks Analyzed
10
Analyzed
Mar 7, 2026, 08:59 PM
Security Audit — runlayer — database-optimizer