Postgres Pro
Downloads
Home   >   mailing lists

Re: how to avoid deadlock on masive update with multiples delete - Mailing list pgsql-performance

From Claudio Freire
Subject Re: how to avoid deadlock on masive update with multiples delete
Date
Msg-id CAGTBQpbK3K56Jzx_xU3ch1QB2TcnbwmQUd0T_98V6BoScGHOMg@mail.gmail.com
Whole thread Raw
In response to Re: how to avoid deadlock on masive update with multiples delete  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: how to avoid deadlock on masive update with multiples delete  (Maciek Sakrejda <m.sakrejda@gmail.com>)
Re: how to avoid deadlock on masive update with multiples delete  ("Anibal David Acosta" <aa@devshock.com>)
List pgsql-performance
Tree view 
On Thu, Oct 4, 2012 at 1:10 PM, Jeff Janes <jeff.janes@gmail.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)

pgsql-performance by date:

Previous
From: Igor Neyman
Date:
Subject: Re: how to avoid deadlock on masive update with multiples delete
Next
From: Maciek Sakrejda
Date:
Subject: Re: how to avoid deadlock on masive update with multiples delete