From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Add bump memory context type and use it for tuplesorts |
Date: | 2023-07-10 23:51:11 |
Message-ID: | CAApHDvrtvHu1d3u5qK7qFef8yY-5FWrjbSh9snYTox-Qt8Kxxw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 27 Jun 2023 at 21:19, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I've attached the bump allocator patch and also the script I used to
> gather the performance results in the first 2 tabs in the attached
> spreadsheet.
I've attached a v2 patch which changes the BumpContext a little to
remove some of the fields that are not really required. There was no
need for the "keeper" field as the keeper block always comes at the
end of the BumpContext as these are allocated in a single malloc().
The pointer to the "block" also isn't really needed. This is always
the same as the head element in the blocks dlist.
David
Attachment | Content-Type | Size |
---|---|---|
bump_allocator_v2.patch | text/plain | 35.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-07-11 00:20:45 | Re: WAL Insertion Lock Improvements |
Previous Message | Jacob Champion | 2023-07-10 23:50:22 | Re: [PoC] Federated Authn/z with OAUTHBEARER |