On Fri, Nov 4, 2011 at 4:07 PM, Claudio Freire <klaussfreire@xxxxxxxxx> wrote: >> Here again, you've set it to ten times the default value. That >> doesn't seem like a good idea. I would start with the default and >> tune down. > > Already did that. Waiting to see how it turns out. Nope, still happening with those changes. Though it did make sense that those settings were too high, it didn't fix the strange blocking. Is it possible that the query is locking all the tuples hit, rather than only the ones selected? Because the index used to reach the tuple has to walk across around 3k tuples before finding the one that needs locking. They're supposed to be in memory already (they're quite hot), that's why selecting is fast, but maybe it's trying to lock all 3k tuples? I don't know, I'm just throwing punches blindly at this point. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
