On Mon, Sep 19, 2011 at 12:54 PM, Vitalii Tymchyshyn <tivv00@xxxxxxxxx> wrote: > 19.09.11 18:19, Robert Klemme написав(ла): >> >> I still haven't seen a solution to locking when a hash table needs >> resizing. All hashing algorithms I can think of at the moment would >> require a lock on the whole beast during the resize which makes this >> type of index impractical for certain loads (heavy updating). > > Sorry for the second reply, I should have not start writing until I've read > all your post. Anyway. > Do you need read lock? I'd say readers could use "old" copy of hash table up > until the moment new bigger copy is ready. This will simply look like the > update is not started yet, which AFAIK is OK for MVCC. > Yep, all the writers will wait. All this would get solved if there's no automatic hash index resizing. DBAs would have to recreate (possibly concurrently) the hash to make it bigger. Still, hash has lots of issues. I'm not sure how the hash is implemented in PG, but usually, for low collision rates pseudorandom walks are used to traverse collision chains. But pseudorandom collision chains mean random I/O which is awful for a DB. Those techniques have not been designed to work with secondary memory. So, they would have to be adapted to working with secondary memory, and that means a lot of R&D. It's not impossible, it's just a lot of work. I subscribe to the idea that, *in the meanwhile*, without scrapping the hash index and in parallel to improving it, an option for transparently-hashed btrees would be valuable. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
