Re: Out of Memory errors are frustrating as heck!
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Gunther <raj@gusw.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-performance@lists.postgresql.org, Jeff Janes <jeff.janes@gmail.com>
Date: 2019-04-15T04:15:00Z
Lists: pgsql-performance
On Sun, Apr 14, 2019 at 11:59:45PM -0400, Gunther wrote: > On 4/14/2019 23:24, Tom Lane wrote: > >Any chance of extracting a self-contained test case that reproduces this? > With 18 million rows involved in the base tables, hardly. Were you able to reproduce the problem with SELECT (without INSERT) ? How many rows does it output ? Show explain analyze if possible. If that still errors, can you make it work with a small enough LIMIT ? We haven't seen the view - maybe it's very complicated, but can you reproduce with a simpler one ? Fewer joins ? Or fewer join conditions ? Justin
Commits
-
Consider BufFiles when adjusting hashjoin parameters
- a1b4f289beec 18.0 landed
-
Allocate hash join files in a separate memory context
- 8c4040edf456 16.0 landed