Re: how to avoid deadlock on masive update with multiples delete

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Anibal David Acosta <aa(at)devshock(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: how to avoid deadlock on masive update with multiples delete
Date: 2012-10-05 14:27:13
Message-ID: CAGTBQpbK3K56Jzx_xU3ch1QB2TcnbwmQUd0T_98V6BoScGHOMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Oct 4, 2012 at 1:10 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> 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.

How do you make pg update/delete records, in bulk, in some particular order?

(ie, without issuing separate queries for each record)

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Maciek Sakrejda 2012-10-05 15:08:19 Re: how to avoid deadlock on masive update with multiples delete
Previous Message Igor Neyman 2012-10-05 14:06:41 Re: how to avoid deadlock on masive update with multiples delete