Re: help with locked table(s)/transactions(s)

From: Mott Leroy <mott(at)acadaca(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: help with locked table(s)/transactions(s)
Date: 2006-02-01 15:01:57
Message-ID: 43E0CD65.4080709@acadaca.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> No, the locks would be held till end of transaction. It is a little odd
> that you have so many conflicts, though, unless the referenced table is
> pretty small and/or this loop manages to touch a large fraction of the
> possible keys.

Ah, well, if the locks are held to the end of the transaction that would
explain it I think. I mean, the loop touches *every* row (UPDATEs) in
one of the tables. It sounds like I need to break up this function into
a smaller function (by placing the loop outside the transaction).

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2006-02-01 15:04:17 Re: Passwords when changing users -> roles
Previous Message Bruce Momjian 2006-02-01 14:59:05 Re: Help in compiling 8.1.2 from source