>
> Well, first off, a btree index is fairly useless for this query,
> because btree has no concept that the hstore has any sub-structure.
> A GIN index or GIST index could work though. Secondly, you have to
> remember that indexable WHERE conditions in Postgres are *always* of
> the form "WHERE i
Michael Barker writes:
> I'm currently experimenting with hstore on Posgtres 9.4rc1. I've created a
> table with an hstore column, with and index on that column (tried both gin
> and btree indexes) and the explain plan says that the index is never used
> for the lookup and falls to a sequential s
On Fri, Dec 05, 2014 at 09:42:20AM +1300, Michael Barker wrote:
> 1) Created table with hstore column and btree index.
>
> barkerm=# \d audit
>Table "public.audit"
> Column |Type |
> Modifiers
> ---+--
Hi,
Apologies if this is the wrong list for this time of query (first time
posting).
I'm currently experimenting with hstore on Posgtres 9.4rc1. I've created a
table with an hstore column, with and index on that column (tried both gin
and btree indexes) and the explain plan says that the index i
