From: Peter Eisentraut <peter@eisentraut.org>
To: David Rowley <dgrowleyml@gmail.com>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Introduce a bump memory allocator
Date: Wed, 10 Apr 2024 09:35:54 +0200
Message-ID: <1e1a098e-b9af-4c95-8dea-7338d1c4e46d@eisentraut.org> (raw)
In-Reply-To: <CAApHDvpKf+6vFoDe1HmqVMkv=cgY1WHP-Kw6=BPaXxGptBP=3g@mail.gmail.com>
References: <E1rtRFE-000y8T-SU@gemulon.postgresql.org>
<5f724fb2-96e1-4f36-b65b-47b337ad432e@eisentraut.org>
<CAApHDvpKf+6vFoDe1HmqVMkv=cgY1WHP-Kw6=BPaXxGptBP=3g@mail.gmail.com>
On 10.04.24 01:11, David Rowley wrote:
> On Wed, 10 Apr 2024 at 00:05, Peter Eisentraut <peter@eisentraut.org> wrote:
>> This patch introduces in bump.c the macro BumpBlockIsValid(), but it's
>> not used anywhere. Can we remove it?
>
> I've just pushed a patch to remove it.
>
> Was that spotted by eagle eyes or tooling?
I used gcc -Wunused-macros. This is somewhat noisy, but occasionally
useful to find leftover stuff.
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, dgrowleyml@gmail.com, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Introduce a bump memory allocator
In-Reply-To: <1e1a098e-b9af-4c95-8dea-7338d1c4e46d@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