Alternatives to very large tables with many performance-killing indicies?

Поиск
Список
Период
Сортировка
Hey folks, a question. We have a table that's getting large (6 million rows right now, but hey, no end in sight). It's wide-ish, too, 98 columns.

The problem is that each of these columns needs to be searchable quickly at an application level, and I'm far too responsible an individual to put 98 indexes on a table. Wondering what you folks have come across in terms of creative solutions that might be native to postgres. I can build something that indexes the data and caches it and runs separately from PG, but I wanted to exhaust all native options first.

Thanks!

--
Wells Oliver
wellsoliver@gmail.com

В списке pgsql-general по дате отправления:

Предыдущее
От: Steve Crawford
Дата:
Сообщение: Re: You cannot do PITR with streaming replication - true?
Следующее
От: Merlin Moncure
Дата:
Сообщение: Re: Alternatives to very large tables with many performance-killing indicies?