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: Justin Pryzby <pryzby@telsasoft.com>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Jeff Janes <jeff.janes@gmail.com>, pgsql-performance@lists.postgresql.org
Date: 2019-04-20T20:47:59Z
Lists: pgsql-performance 
Gunther <raj@gusw.net> writes:
> and checked my log file and there was nothing before the call 
> MemoryContextStats(TopPortalContext) so I don't understand where this 
> printf stuff is ending up.

It's going to stdout, which is likely block-buffered whereas stderr
is line-buffered, so data from the latter will show up in your log
file much sooner.  You might consider adding something to startup
to switch stdout to line buffering.

			regards, tom lane

Commits

  1. Consider BufFiles when adjusting hashjoin parameters

  2. Allocate hash join files in a separate memory context