Re: lock problem - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: lock problem
Date
Msg-id 4EF1B04D0200002500043F4C@gw.wicourts.gov
Whole thread Raw
In response to Re: lock problem  (Rural Hunter <ruralhunter@gmail.com>)
Responses Re: lock problem  (Rural Hunter <ruralhunter@gmail.com>)
List pgsql-admin
Rural Hunter <ruralhunter@gmail.com> wrote:

> I still have this question:
> same statement A,B,C,D update same row. The start order is
> A->B->C-D.  From what I've gotten, B/C/D got the lock before A.
> Why did that happen?

Did you do anything to prevent it from happening?  If not, the OS
scheduler is going to give time to one process or another in a
fairly unpredictable way.

-Kevin

pgsql-admin by date:

Previous
From: Rural Hunter
Date:
Subject: Re: lock problem
Next
From: Tom Lane
Date:
Subject: Re: stats and unix sockets