Re: Excessive memory usage in multi-statement queries w/ partitioning - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Excessive memory usage in multi-statement queries w/ partitioning
Date
Msg-id 65092.1558961789@sss.pgh.pa.us
Whole thread Raw
In response to Re: Excessive memory usage in multi-statement queries w/ partitioning  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: Excessive memory usage in multi-statement queries w/ partitioning  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes:
> On 2019/05/24 23:28, Tom Lane wrote:
>> So my thought, if we want to do something about this, is not "find
>> some things we can pfree at the end of planning" but "find a way
>> to use a separate context for each statement in the query string".

> Maybe like the attached?  I'm not sure if we need to likewise be concerned
> about exec_sql_string() being handed multi-query strings.

Please add this to the upcoming CF so we don't forget about it.
(I don't think there's anything very new about this behavior, so
I don't feel that we should consider it an open item for v12 ---
anyone think differently?)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Khandekar
Date:
Subject: Re: Minimal logical decoding on standbys
Next
From: Tom Lane
Date:
Subject: Re: BEFORE UPDATE trigger on postgres_fdw table not work