Re: [GENERAL] Non-overlapping updates blocking each other - Mailing list pgsql-general

From Thomas Kellerer
Subject Re: [GENERAL] Non-overlapping updates blocking each other
Date
Msg-id ortcce$52o$1@blaine.gmane.org
Whole thread Raw
In response to Re: [GENERAL] Non-overlapping updates blocking each other  (Melvin Davidson <melvin6925@gmail.com>)
Responses Re: [GENERAL] Non-overlapping updates blocking each other  (Melvin Davidson <melvin6925@gmail.com>)
List pgsql-general
Melvin Davidson schrieb am 14.10.2017 um 17:32:
> More than likely, the optimizer has determined that a table scan is best, in which case it will use a table lock.
> That means one updates will be blocking each other.

Since when does Postgres lock the whole table during an update?





-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Melvin Davidson
Date:
Subject: Re: [GENERAL] Non-overlapping updates blocking each other
Next
From: Melvin Davidson
Date:
Subject: Re: [GENERAL] Non-overlapping updates blocking each other