| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Gunther <raj(at)gusw(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)lists(dot)postgresql(dot)org, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Subject: | Re: Out of Memory errors are frustrating as heck! |
| Date: | 2019-04-15 04:15:00 |
| Message-ID: | 20190415041500.GK29543@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2019-04-15 13:32:09 | Re: Out of Memory errors are frustrating as heck! |
| Previous Message | Gunther | 2019-04-15 03:59:45 | Re: Out of Memory errors are frustrating as heck! |