bug-bounty252
google211
facebook176
microsoft172
apple125
rce95
exploit88
xss57
defi48
smart-contract47
writeup47
ethereum44
open-source44
access-control42
sqli39
aws37
ai-agents36
docker36
csrf36
web335
account-takeover35
ssrf35
malware34
bragging-post33
cloudflare33
smart-contract-vulnerability33
react32
dos31
cve31
subdomain-takeover27
supply-chain26
idor26
privilege-escalation25
solidity25
wordpress23
browser23
cors23
node22
denial-of-service21
authentication-bypass21
oauth21
automation20
race-condition20
vulnerability-disclosure19
auth-bypass19
tool19
cloud19
machine-learning18
llm17
pentest17
0
7/10
tutorial
A deep dive into PostgreSQL memory management failures caused by work_mem misunderstandings: a single poorly-written query combining a plpgsql function with hash joins accumulated 2 TB of RAM because memory contexts are only released at query completion, not per-operation. The article explains root causes, introduces pg_log_backend_memory_contexts for debugging, and provides mitigation strategies including query rewrites and statement timeouts.
postgresql
memory-management
performance-tuning
work-mem
query-optimization
oom-killer
postgres-internals
memory-context
hash-join
plpgsql
dba-troubleshooting
PostgreSQL
pg_log_backend_memory_contexts
Henrietta Dombrovskaya
Nordic PGDay 2026
ExecutorState
HashTableContext