Stefan Keller writes:
> Hi Tom, hi all
> Thanks, Tom, for your tipps. You answered 2011/5/1:
>> (...), and there's no point in having the
>> index column contents be the entire tags value (which is what's leading
>> to the failure). Consider
>>
>> create index planet_osm_point_amenity on planet_
Hi Tom, hi all
Thanks, Tom, for your tipps. You answered 2011/5/1:
> (...), and there's no point in having the
> index column contents be the entire tags value (which is what's leading
> to the failure). Consider
>
> create index planet_osm_point_amenity on planet_osm_point ((tags->amenity));
To
Stefan Keller writes:
> I'm doing an equality search with success with the '->' operator on
> the same field 'tags' like in this query (1):
> -- Count all restaurants in database ("amenity = restaurant''):
> select count(*) from osm_all_v
> where hstore(tags)->'amenity'='restaurant'
> This query
Hi Tom,
Thanks for the hint! I'm actually doing a GROUP BY with an inquality
search (HAVING...) and still get long lasting queries, see query (2)
below.
I'm doing an equality search with success with the '->' operator on
the same field 'tags' like in this query (1):
-- Count all restaurants in
Stefan Keller writes:
> Any ideas on how to index my hstore attribute?
Use a GIST or GIN index. The only thing that a btree index on hstore
can do for you is to support equality comparisons on the whole hstore
value, which is pretty unlikely to be what you're after.
rega
Hi,
2011/3/13 Viktor Nagy
> when trying to insert a long-long value, I get the following error:
>
> ERROR: Index row size 3120 exceeds maximum 2712 for index
> "ir_translation_ltns"
> HINT: Values larger than 1/3 of a buffer page cannot be indexed.
> Consider a function index of an MD5 hash of
