Re: Performant queries on table with many boolean columns - Mailing list pgsql-performance

From David G. Johnston
Subject Re: Performant queries on table with many boolean columns
Date
Msg-id CAKFQuwY3z7oGwriDie4guGPudy_k8S4wWJKrTRy7zPKjTUm=wQ@mail.gmail.com
Whole thread Raw
In response to Re: Performant queries on table with many boolean columns  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: Performant queries on table with many boolean columns  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-performance
On Wed, Apr 20, 2016 at 11:54 AM, Teodor Sigaev <teodor@sigaev.ru> wrote:

The obvious thing seems to make a table with ~100 columns, with 1 column
for each boolean property. Though, what type of indexing strategy would
one use on that table? Doesn't make sense to do BTREE. Is there a better
way to structure it?

looks like a deal for contrib/bloom index in upcoming 9.6 release

​Curious, it doesn't look like it will work with booleans out of the box.


David J.
 

pgsql-performance by date:

Previous
From: Rick Otten
Date:
Subject: Re: Performant queries on table with many boolean columns
Next
From: "Sven Kerkling"
Date:
Subject: Performance problems with postgres and null Values?