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 CAGTBQpaN6zwr=-EQYYC4cR4iK0PaKTTckA3ChBzppu90rYwJuQ@mail.gmail.com
Whole thread Raw
In response to Re: how to avoid deadlock on masive update with multiples delete  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On Fri, Oct 5, 2012 at 12:46 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>         FOR c IN SELECT ctid FROM table WHERE ... ORDER BY ... LOOP
>                 DELETE FROM table WHERE ctid = c;
>         END LOOP;

Maybe, in that sense, it would be better to optimize client-server
protocol for batch operations.

PREPARE blah(c) AS DELETE FROM table WHERE ctid = $1;

EXECUTE blah(c1), blah(c2), blah(c3), ...
 ^ 1 transaction, 1 roundtrip, multiple queries


pgsql-performance by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: how to avoid deadlock on masive update with multiples delete
Next
From: Tom Lane
Date:
Subject: Re: how to avoid deadlock on masive update with multiples delete