bug-bounty267
google223
facebook191
microsoft178
apple129
exploit104
rce99
xss88
writeup55
csrf52
defi48
smart-contract47
ethereum44
open-source44
access-control42
account-takeover39
sqli39
aws37
docker36
ssrf36
ai-agents36
web335
malware35
bragging-post33
smart-contract-vulnerability33
cloudflare33
cve32
react32
dos31
idor28
subdomain-takeover27
wordpress26
browser26
privilege-escalation26
supply-chain26
solidity25
cors24
oauth23
node22
authentication-bypass21
auth-bypass21
cloud21
race-condition21
denial-of-service21
automation20
tool19
lfi19
pentest19
vulnerability-disclosure19
machine-learning18
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