From: Tom Lane <tgl@sss.pgh.pa.us>
To: harukat@sraoss.co.jp
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18353: PG16.2 release note doc bug in "In contrib/bloom, fix overly tight assertion ..."
Date: Tue, 20 Feb 2024 11:34:41 -0500
Message-ID: <199833.1708446881@sss.pgh.pa.us> (raw)
In-Reply-To: <18353-926aa99cfe58aa78@postgresql.org>
References: <18353-926aa99cfe58aa78@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> In the release note for 16.2, 15.6 and 14.11, the following entry looks
> wrong.
> The fix is not on contrib/bloom but BRIN's bloom operator class.
You're right, I misread the commit log entry. I'll adjust this,
although it won't show up anywhere till the next quarterly
releases.
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, harukat@sraoss.co.jp, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18353: PG16.2 release note doc bug in "In contrib/bloom, fix overly tight assertion ..."
In-Reply-To: <199833.1708446881@sss.pgh.pa.us>
* 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