On Mar 30, 2005, at 4:47 PM, Alvaro Herrera wrote:
> Now this can't be applied right away because it's easy to run "out of
> memory" (shared memory for the lock table). Say, a delete or update
> that touches 10000 tuples does not work. I'm currently working on a
> proposal to allow the lock table to spill to disk ...
>
That would be most excellent, as I have deadlocks from transactions
that do upwards of 100k inserts selecting data from other tables.
