pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: harukat@sraoss.co.jp
Subject: BUG #18353: PG16.2 release note doc bug in "In contrib/bloom, fix overly tight assertion ..."
Date: Tue, 20 Feb 2024 07:37:06 +0000
Message-ID: <18353-926aa99cfe58aa78@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      18353
Logged by:          TAKATSUKA Haruka
Email address:      harukat@sraoss.co.jp
PostgreSQL version: 16.2
Operating system:   ANY
Description:        

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.

    <listitem>
<!--
Author: Michael Paquier <michael@paquier.xyz>
Branch: master [1b2c6b756] 2023-11-08 14:06:26 +0900
Branch: REL_16_STABLE [4dccf9575] 2023-11-08 14:06:36 +0900
Branch: REL_15_STABLE [7e18c0bd6] 2023-11-08 14:06:39 +0900
Branch: REL_14_STABLE [59fc39c0d] 2023-11-08 14:06:42 +0900
-->
     <para>
      In <filename>contrib/bloom</filename>, fix overly tight assertion
      about <varname>false_positive_rate</varname> (Alexander Lakhin)
     </para>
    </listitem>



view thread (2+ messages)  latest in thread

Message-ID: <18353-926aa99cfe58aa78@postgresql.org>
Permalink:  ../18353-926aa99cfe58aa78@postgresql.org/
Also on:    postgresql.org/message-id/18353-926aa99cfe58aa78@postgresql.org

 · 

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-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, harukat@sraoss.co.jp
  Subject: Re: BUG #18353: PG16.2 release note doc bug in "In contrib/bloom, fix overly tight assertion ..."
  In-Reply-To: <18353-926aa99cfe58aa78@postgresql.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