From: Peter Eisentraut <peter@eisentraut.org>
To: David Rowley <drowley@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Introduce a bump memory allocator
Date: Tue, 9 Apr 2024 14:05:30 +0200
Message-ID: <5f724fb2-96e1-4f36-b65b-47b337ad432e@eisentraut.org> (raw)
In-Reply-To: <E1rtRFE-000y8T-SU@gemulon.postgresql.org>
References: <E1rtRFE-000y8T-SU@gemulon.postgresql.org>
On 07.04.24 14:03, David Rowley wrote:
> Introduce a bump memory allocator
This patch introduces in bump.c the macro BumpBlockIsValid(), but it's
not used anywhere. Can we remove it?
(If we don't remove it, I suggest to make it an inline function, so it's
easier to tell what it's supposed to be called with. Especially with
the BumpIsValid() nearby, it can be a bit confusing.)
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-committers@postgresql.org
Cc: peter@eisentraut.org, drowley@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Introduce a bump memory allocator
In-Reply-To: <5f724fb2-96e1-4f36-b65b-47b337ad432e@eisentraut.org>
* 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