In my use, mainly arrays and hstore cols, including arrays of hstores. These are column types that I suspect benefit from indexes more than most column types.
depends on usage
when you use a arrays for time series, then you don't use a index usually
and in hstore, you should to decide between GiST or GIN index. What should be default?
I don't think so this feature is a good idea. Maybe enhancing a domains about possibility to specify a index type for domain.
I don't see indication that the capability described below exists in Postgres (or any RDBMS), so this is likely a feature request --
For column types that are frequently defined in tables, and which are typically indexed, it would be helpful to be able to specify in the type definition of the column that its addition/creation into a table should be automatically accompanied by the creation of an associated index.
Auto-index generation for a specific column type would be overridable for specific tables, as you wouldn't always want to auto-create an index at the time of column addition to a table. In the case of CREATE TABLE, this would be less of a concern, and more of a concern for ALTER TABLE ADD COLUMN.
Such a configuration would also specify the type of index.
What do you think ?
It is relatively dangerous, I think. What is typical type that can be indexed?