pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Petr Jelinek <petr@2ndquadrant.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: John Gorman <johngorman2@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: PATCH: two slab-like memory allocators
Date: Sun, 27 Nov 2016 19:25:17 +0100
Message-ID: <9cdbe694-1b49-0c61-b0b2-d95ef2b3cb31@2ndquadrant.com> (raw )
In-Reply-To: <0b14e90b-1985-bb04-0261-2fcdc28755ab@2ndquadrant.com >
References: <CALkS6B8hisTEJJ7ZCQ_GiBLNVzKfsevAD+92rYN6myyFK=UQtw@mail.gmail.com >
<11821eb9-95a5-353e-ccba-13e8e9351e62@2ndquadrant.com >
<b8ded0aa-2515-7ffd-162b-8f515df5eca1@2ndquadrant.com >
<CA+Tgmob7u4thiBbdvyseQk1aVApJeG10C_rFFt8LPV03-UzD7g@mail.gmail.com >
<a4593432-c989-8ec4-2320-943e3f97ce6d@2ndquadrant.com >
<CA+TgmobJrM74FRTcmn2JDMVbLB0a5pj5e3ieLBMzkDNtrxF4dw@mail.gmail.com >
<9818b54a-fcb6-f018-0b16-96d6a1d1da27@2ndquadrant.com >
<34a6d4ea-7f3d-a62c-fff1-7a9108c078d7@2ndquadrant.com >
<f2aaf4a5-412c-a4b9-389d-c9f682fbdc77@2ndquadrant.com >
<4f176a6c-c197-165d-dee4-5de8f279f1f4@2ndquadrant.com >
<20161112191257.3a4n6kzegvu637qn@alap3.anarazel.de >
<efd47210-cf95-d7ee-e984-a873f76596a8@2ndquadrant.com >
<0b14e90b-1985-bb04-0261-2fcdc28755ab@2ndquadrant.com >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 15/11/16 01:44, Tomas Vondra wrote:
> Attached is v6 of the patch series, fixing most of the points:
>
> * common bits (valgrind/randomization/wipe) moved to memdebug.h/c
>
> Instead of introducing a new header file, I've added the prototypes to
> memdebug.h (which was already used for the valgrind stuff anyway), and
> the implementations to a new memdebug.c file. Not sure what you meant by
> "static inlines" though.
I think Andres wanted to put the implementation to the static inline
functions directly in the header (see parts of pg_list or how atomics
work), but I guess you way works too.
>
> I've however kept SlabContext->freelist as an array, because there may
> be many blocks with the same number of free chunks, in which case moving
> the block in the list would be expensive. This way it's simply
> dlist_delete + dlist_push.
>
+1
I get mxact isolation test failures in test_decoding with this version
of patch:
step s0w: INSERT INTO do_write DEFAULT VALUES;
+ WARNING: problem in slab TXN: number of free chunks 33 in block
0x22beba0 does not match bitmap 34
step s0start: SELECT data FROM
pg_logical_slot_get_changes('isolation_slot', NULL, NULL,
'include-xids', 'false');
data
and
step s0alter: ALTER TABLE do_write ADD column ts timestamptz;
step s0w: INSERT INTO do_write DEFAULT VALUES;
+ WARNING: problem in slab TXN: number of free chunks 33 in block
0x227c3f0 does not match bitmap 34
step s0start: SELECT data FROM
pg_logical_slot_get_changes('isolation_slot', NULL, NULL,
'include-xids', 'false');
data
Also, let's just rename the Gen to Generation.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (97+ messages) latest in thread
Message-ID: <9cdbe694-1b49-0c61-b0b2-d95ef2b3cb31@2ndquadrant.com>
Permalink: ../9cdbe694-1b49-0c61-b0b2-d95ef2b3cb31@2ndquadrant.com/
Also on: postgresql.org/message-id/9cdbe694-1b49-0c61-b0b2-d95ef2b3cb31@2ndquadrant.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: petr@2ndquadrant.com, tomas.vondra@2ndquadrant.com, andres@anarazel.de, robertmhaas@gmail.com, johngorman2@gmail.com
Subject: Re: PATCH: two slab-like memory allocators
In-Reply-To: <9cdbe694-1b49-0c61-b0b2-d95ef2b3cb31@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox