| From: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tv(at)fuzzy(dot)cz> |
| Subject: | Re: Use generation context to speed up tuplesorts |
| Date: | 2021-12-17 10:20:11 |
| Message-ID: | 4697108.irdbgypaU6@aivenronan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le vendredi 17 décembre 2021, 09:08:06 CET Ronan Dunklau a écrit :
> It is my understanding that malloc will try to compact memory by moving it
> around. So the memory should be actually be released to the kernel at some
> point. In the meantime, malloc can reuse it for our next invocation (which
> can be in a different memory context on our side).
I've been told off-list this comment wasn't clear: I meant that it compacts
*free* memory, consolidating into larger blocks that will eventually reach the
threshold, and be released.
--
Ronan Dunklau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-12-17 10:59:55 | Re: row filtering for logical replication |
| Previous Message | Amit Kapila | 2021-12-17 10:12:10 | Re: Skipping logical replication transactions on subscriber side |