postgres.git / summary / log / commit / refs

commit    872b6f72d419a7fb2bc18236ee70175e8ff2abf0
Author:   Alexander Korotkov <akorotkov@postgresql.org>
Date:     Sun Oct 14 21:40:17 2018 +0000
First released in: 12.0, 9.6.11, 10.6, 11.0

    contrib/bloom documentation improvement
    
    This commit documents rounding of "length" parameter and absence of support
    for unique indexes and NULLs searching.  Backpatch to 9.6 where contrib/bloom
    was introduced.
    
    Discussion: https://postgr.es/m/CAF4Au4wPQQ7EHVSnzcLjsbY3oLSzVk6UemZLD1Sbmwysy3R61g%40mail.gmail.com
    Author: Oleg Bartunov with minor editorialization by me
    Backpatch-through: 9.6


 doc/src/sgml/bloom.sgml | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/bloom.sgml b/doc/src/sgml/bloom.sgml
index 396348c5237..2eb7a4fd40d 100644
--- a/doc/src/sgml/bloom.sgml
+++ b/doc/src/sgml/bloom.sgml
@@ -51,8 +51,8 @@
     <term><literal>length</></term>
     <listitem>
      <para>
-      Length of each signature (index entry) in bits. The default
-      is <literal>80</> bits and maximum is <literal>4096</>.
+      Length of each signature (index entry) in bits, it is rounded up to the nearest
+      multiple of <literal>16</>. The default is <literal>80</> bits and maximum is <literal>4096</literal>.
      </para>
     </listitem>
    </varlistentry>
@@ -242,6 +242,20 @@ DEFAULT FOR TYPE text USING bloom AS
       operations in the future.
      </para>
     </listitem>
+
+    <listitem>
+     <para>
+       <literal>bloom</literal> access method doesn't support
+       <literal>UNIQUE</literal> indexes.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+       <literal>bloom</literal> access method doesn't support searching for
+       <literal>NULL</literal> values.
+     </para>
+    </listitem>
    </itemizedlist>
   </para>
  </sect2>


[parent: 8384ff42486e]