pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes 6+ messages / 1 participants [nested] [flat]
* pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes @ 2024-12-09 20:25 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: David Rowley @ 2024-12-09 20:25 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes @ 2024-12-09 20:25 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: David Rowley @ 2024-12-09 20:25 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/f36fe5d07bf94c97cfb6b3f3eefef47702a70e97 Modified Files -------------- doc/src/sgml/bloom.sgml | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes @ 2024-12-09 20:26 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: David Rowley @ 2024-12-09 20:26 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b0a04ce0916b370e70ccf0a2e6a5d4d7607efe25 Modified Files -------------- doc/src/sgml/bloom.sgml | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes @ 2024-12-09 20:26 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: David Rowley @ 2024-12-09 20:26 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/5e9e2a4ac7bbdc5a8c8ec06f1b6ac78cfb5fca67 Modified Files -------------- doc/src/sgml/bloom.sgml | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes @ 2024-12-09 20:26 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: David Rowley @ 2024-12-09 20:26 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4922ede979947bc2404e8675435184e61a57a530 Modified Files -------------- doc/src/sgml/bloom.sgml | 50 ++++++++++++++++++++++++------------------------- 1 file changed, 25 insertions(+), 25 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes @ 2024-12-09 20:27 David Rowley <drowley@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: David Rowley @ 2024-12-09 20:27 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/a51ec088dbe54c41ecb3178053da8881d0e2452e Modified Files -------------- doc/src/sgml/bloom.sgml | 48 ++++++++++++++++++++++++------------------------ 1 file changed, 24 insertions(+), 24 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2024-12-09 20:27 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-12-09 20:25 pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes David Rowley <drowley@postgresql.org> 2024-12-09 20:25 pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes David Rowley <drowley@postgresql.org> 2024-12-09 20:26 pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes David Rowley <drowley@postgresql.org> 2024-12-09 20:26 pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes David Rowley <drowley@postgresql.org> 2024-12-09 20:26 pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes David Rowley <drowley@postgresql.org> 2024-12-09 20:27 pgsql: Doc: fix incorrect EXPLAIN ANALYZE output for bloom indexes David Rowley <drowley@postgresql.org>
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