On Thu, Oct 4, 2012 at 7:01 AM, Anibal David Acosta <aa@xxxxxxxxxxxx> wrote: > Hi, > > I have a table with about 10 millions of records, this table is update and > inserted very often during the day (approx. 200 per second) , in the night > the activity is a lot less, so in the first seconds of a day (00:00:01) a > batch process update some columns (used like counters) of this table > setting his value to 0. > > > > Yesterday, the first time it occurs, I got a deadlock when other process try > to delete multiple (about 10 or 20) rows of the same table. ... > > Any ideas how to prevent this situation? The bulk update could take an Exclusive (not Access Exclusive) lock. Or the delete could perhaps be arranged to delete the records in ctid order (although that might still deadlock). Or you could just repeat the failed transaction. Cheers, Jeff -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
