Postgres doesn't fancy many small and frequent updates (like rapid counter increments). It is workable, though, via combination of batching, ensuyring indexes

Postgres doesn't fancy many small and frequent updates (like rapid counter increments). It is workable, though, via combination of batching, ensuyring indexes on hot fields have appropriate fillfactor, and making sure Postgres can use heap-only tuples. Here's my old SO question on this and a well-comprehensive answer that's still actual and could be helpful for some cases: http://stackoverflow.com/a/1663434/116546 http://stackoverflow.com/a/1663434/116546