Re: [BUGS] BUG #14843: CREATE TABLE churns through all memory,crashes db
От | Michael Paquier |
---|---|
Тема | Re: [BUGS] BUG #14843: CREATE TABLE churns through all memory,crashes db |
Дата | |
Msg-id | CAB7nPqRjCoFMFVb7RcG5ztxzmobALij0O21m3-p8qNbxw37ouA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #14843: CREATE TABLE churns through all memory,crashes db (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [BUGS] BUG #14843: CREATE TABLE churns through all memory,crashes db
|
Список | pgsql-bugs |
On Fri, Oct 6, 2017 at 10:00 AM, Michael Paquier <michael.paquier@gmail.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@anarazel.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: