| From: | David Rowley <drowley(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes |
| Date: | 2024-12-09 20:25:14 |
| Message-ID: | E1tKkJd-001v9K-Ih@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes
It looks like the example case was once modified to increase the number
of rows but the EXPLAIN ANALYZE output wasn't updated to reflect that.
Also adjust the text which discusses the index sizes. With the example
table size, the bloom index isn't quite 8 times more space efficient
than the btree indexes.
Discussion: https://postgr.es/m/CAApHDvovx8kQ0=HTt85gFDAwmTJHpCgiSvRmQZ_6u_g-vQYM_w@mail.gmail.com
Backpatch-through: 13, all supported versions
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/36d0229b8ff5907ccff782e9425d1647401b7e99
Modified Files
--------------
doc/src/sgml/bloom.sgml | 42 +++++++++++++++++++++---------------------
1 file changed, 21 insertions(+), 21 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2024-12-09 20:25:43 | pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes |
| Previous Message | Daniel Gustafsson | 2024-12-09 20:01:26 | pgsql: Fix small memory leaks in GUC checks |