BUG #17443: Select command does not use brin index when enable_seqscan = on

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: ronivaldolopes(at)hotmail(dot)com
Subject: BUG #17443: Select command does not use brin index when enable_seqscan = on
Date: 2022-03-21 02:44:08
Message-ID: 17443-543da4d6744b8ef2@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17443
Logged by: Ronivaldo Lopes
Email address: ronivaldolopes(at)hotmail(dot)com
PostgreSQL version: 14.2
Operating system: Linux Mint
Description:

For the select command to use the brin index of the id2 field, I have to
change enable_seqscan = off

create temp table teste as
select s::int as id1, s::int as id2, quote_ident('Nome ' || to_char(s,
'FM00000000'))::varchar(15) as nome
from generate_series(1,10000000) x(s);

create index teste1 on teste (id1);
create index teste2 on teste using brin (id2);

EXPLAIN (analyze on, wal on, verbose on, format text)
select id1 from teste where id1 = 1000000;

EXPLAIN (analyze on, wal on, verbose on, format text)
select id2 from teste where id2 = 1000000;

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Julien Rouhaud 2022-03-21 09:21:58 Re: BUG #17443: Select command does not use brin index when enable_seqscan = on
Previous Message PG Bug reporting form 2022-03-20 21:27:35 BUG #17442: Wrong partition pruning when using prepared statement and huge RAM consumption