| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | ropeladder(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: BUG #14843: CREATE TABLE churns through all memory, crashes db |
| Date: | 2017-10-06 03:57:59 |
| Message-ID: | CAB7nPqRjCoFMFVb7RcG5ztxzmobALij0O21m3-p8qNbxw37ouA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 6, 2017 at 10:00 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> This is suspicious:
> ExecutorState: 62906368 total in 17 blocks; 13736 free (35
> chunks); 62892632 used
The introduction of the ProjectSet node has caused the regressionin
the executor visibly. A bisect run is showing me this commit as the
culprit
commit 69f4b9c85f168ae006929eec44fc44d569e846b9
Author: Andres Freund <andres(at)anarazel(dot)de>
Date: Wed Jan 18 12:46:50 2017 -0800
Move targetlist SRF handling from expression evaluation to new executor node.
I was expecting a leak of some kind first, but valgrind does not
complain when executing the query eating all the memory. Before this
commit the memory usage remains low and stable, less than 1% in my
environments.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-10-06 05:21:05 | Re: pg_logical_slot_peek_changes crashes postgres when called from inside pl/pgsql |
| Previous Message | Michael Paquier | 2017-10-06 01:32:45 | Re: BUG #14843: CREATE TABLE churns through all memory, crashes db |