bug-bounty273
google223
facebook189
microsoft177
apple129
exploit103
rce96
xss88
csrf53
writeup51
defi48
smart-contract47
ethereum44
open-source44
access-control44
account-takeover40
sqli39
bragging-post38
ssrf37
aws37
docker36
ai-agents36
web335
malware35
smart-contract-vulnerability33
react32
dos31
cve31
cloudflare30
idor28
subdomain-takeover28
privilege-escalation27
wordpress26
supply-chain26
browser26
authentication-bypass25
solidity25
oauth23
node22
cors22
race-condition21
auth-bypass21
denial-of-service21
cloud21
automation20
api-security19
tool19
vulnerability-disclosure19
machine-learning18
clickjacking18
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