pgsql: Use the new "Slab" context for some allocations in reorderbuffer

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use the new "Slab" context for some allocations in reorderbuffer
Date: 2017-02-27 12:01:18
Message-ID: E1ciJzS-0005mH-D4@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use the new "Slab" context for some allocations in reorderbuffer.h.

Note that this change alone does not yet fully address the performance
problems triggering this work, a large portion of the slowdown is
triggered by the tuple allocator, which isn't converted to the new
allocator. It would be possible to do so, but using evenly sized
objects, like both the current implementation in reorderbuffer.c and
slab.c, wastes a fair amount of memory. A later patch by Tomas will
introduce a better approach.

Author: Tomas Vondra
Reviewed-By: Andres Freund
Discussion: https://postgr.es/m/d15dff83-0b37-28ed-0809-95a5cc7292ad@2ndquadrant.com

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/9fab40ad32efa4038d19eaed975bb4c1713ccbc0

Modified Files
--------------
src/backend/replication/logical/reorderbuffer.c | 74 ++++++-------------------
src/include/replication/reorderbuffer.h | 14 ++---
2 files changed, 22 insertions(+), 66 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-02-27 13:58:06 pgsql: chomp PQerrorMessage() in backend uses
Previous Message Magnus Hagander 2017-02-26 20:32:41 pgsql: Clarify the role of checkpoint at the begininng of base backups