On Wed, Apr 20, 2016 at 11:54 AM, Teodor Sigaev <teo...@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
Not without doing a custom compilation with an increased INDEX_MAX_KEYS: ERROR: cannot use more than 32 columns in an index But even so, I'm skeptical this would do better than a full scan. It would be interesting to test that. Cheers, Jeff -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
