Re: [GENERAL] Non-overlapping updates blocking each other

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