Re: Parallel Insert and Delete operation
| От | Yelai, Ramkumar IN BLR STS |
|---|---|
| Тема | Re: Parallel Insert and Delete operation |
| Дата | |
| Msg-id | 13D0F6C9B3073A4999E61CAAD61AE7ECC5E84B1704@INBLRK77M2MSX.in002.siemens.net обсуждение исходный текст |
| Ответ на | Re: Parallel Insert and Delete operation ("Albe Laurenz" <laurenz.albe@wien.gv.at>) |
| Список | pgsql-general |
Ramkumar Yelai wrote: [is worried that a database might become inconsistent if conflicting INSERTs and DELETEs occur] > @Albe - I got you first point. The second point is little skeptical because postgres could have been > avoided this lock by using MVCC. Please correct me if I am wrong? Which lock could have been avoided? PostgreSQL locks rows when the data change. That has little to do with MVCC. If you INSERT into a table that has a foreign key, the referenced row in the referenced table gets a SHARE lock that conflictswith the EXCLUSIVE lock required for a DELETE. So they cannot execute concurrently. Yours, Laurenz Albe Thanks very much Albe. I am not aware of that, delete will lock the table.
В списке pgsql-general по дате отправления: