Re: lock problem - Mailing list pgsql-admin

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

> I'm seeing connection hang issue these days. many concurrent
> connections are hanging on db. They basically do the same thing:
> update different rows in same table. The sql itself should run very
> fast as it's updating just one row based on an unique key.

> update article set tm_update=$

I don't see a WHERE clause, so it looks like you're updating the
whole table each time.  Once a row is updated by one of the
transactions, others will block on attempts to update the same row
until the first transaction commits.

-Kevin


pgsql-admin by date:

Previous
From: Rural Hunter
Date:
Subject: lock problem
Next
From: Bèrto ëd Sèra
Date:
Subject: Re: lock problem