Jeff Janes wrote:

one hstore field can easily be equivalent to 50 text fields with
an index on each one.

I'm pretty sure that that is your bottleneck.
I agree that seems like the most likely cause. Each update to the
row holding the hstore column requires adding new index entries for
all the hstore elements, and autovacuum will need to clean up the
old ones in the background. The best solution would be to either
normalize the data instead of using hstore, or move the hstore to a
separate table which is referenced by some sort of ID from the
frequently-updated table.

-Kevin

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 27 of 38 | next ›
Discussion Overview
grouppgsql-general @
categoriespostgresql
postedJan 21, '13 at 8:04a
activeJan 27, '13 at 10:28a
posts38
users9
websitepostgresql.org
irc#postgresql

People

Translate

site design / logo © 2021 Grokbase