Postgres Pro
Downloads
Home   >   mailing lists

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

From Melvin Davidson
Subject Re: [GENERAL] Non-overlapping updates blocking each other
Date
Msg-id CANu8FiwkupSxCdtZF4CRvtVEmGKHmbgqNN2POuh3hawF3War1w@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Non-overlapping updates blocking each other  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: [GENERAL] Non-overlapping updates blocking each other  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tree view


On Sat, Oct 14, 2017 at 12:01 PM, Thomas Kellerer <spam_eater@gmx.net> wrote:
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


>Since when does Postgres lock the whole table during an update?
When the optimizer thinks it needs to do a TABLE SCAN!

--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: [GENERAL] Non-overlapping updates blocking each other
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Non-overlapping updates blocking each other