From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | dwe(at)dbi-services(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Instead of using the bloom index, a parallel sequencial scan is used with this example |
Date: | 2019-11-05 20:02:51 |
Message-ID: | 20191105200251.GA32473@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Oct 24, 2019 at 03:17:06PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/bloom.html
> Description:
I cleaned up your script and created an SQL file that can be piped into
psql, attached. I see the bloomidx index being used without and with
the ANALYZE, output attached. I tested this on git master, and back
through PG 10. Would you please run these queries and post the output:
SELECT version();
SELECT name, current_setting(name), source
FROM pg_settings
WHERE source NOT IN ('default', 'override');
My guess is that you have some non-default setting that is causing
bloomidx not to be used.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
Attachment | Content-Type | Size |
---|---|---|
bloom.sql | application/x-sql | 617 bytes |
out.txt | text/plain | 1.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-11-05 20:11:45 | Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented |
Previous Message | Bruce Momjian | 2019-11-05 17:13:06 | Re: uniqueness and null could benefit from a hint for dba |