Thread

Commits

  1. Doc: correct minor error in back-branch release notes.

  1. BUG #18353: PG16.2 release note doc bug in "In contrib/bloom, fix overly tight assertion ..."

    The Post Office <noreply@postgresql.org> — 2024-02-20T07:37:06Z

    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>
    
    
  2. Re: BUG #18353: PG16.2 release note doc bug in "In contrib/bloom, fix overly tight assertion ..."

    Tom Lane <tgl@sss.pgh.pa.us> — 2024-02-20T16:34:41Z

    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