Horton

Re: Out of Memory errors are frustrating as heck!

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gunther <raj@gusw.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Jeff Janes <jeff.janes@gmail.com>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, pgsql-performance@lists.postgresql.org, Justin Pryzby <pryzby@telsasoft.com>
Date: 2019-04-16T02:50:51Z
Lists: pgsql-performance 
Gunther <raj@gusw.net> writes:
> Is there a way of dumping that memory map info during normal runtime, by 
> calling a function with the debugger?

Sure, "call MemoryContextStats(TopMemoryContext)"

(or actually, since you know which context is the problematic one,
just print that one context)

			regards, tom lane

Commits

  1. Consider BufFiles when adjusting hashjoin parameters

  2. Allocate hash join files in a separate memory context