Re: SSI predicate locking on heap -- tuple or row?
| От | Robert Haas |
|---|---|
| Тема | Re: SSI predicate locking on heap -- tuple or row? |
| Дата | |
| Msg-id | BANLkTiknh-QyVOU9NXeR+mrj_+oR4UqcUQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: SSI predicate locking on heap -- tuple or row? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: SSI predicate locking on heap -- tuple or row?
|
| Список | pgsql-hackers |
On Mon, May 23, 2011 at 10:20 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Aidan Van Dyk <aidan@highrise.ca> writes: >> So, if SSI conflicts something on the UPDATE case, it would necessrily >> have to conflict the DELETE+INSERT case as well, and vice-versa. > > This argument is fundamentally bogus, because an UPDATE is not the same > thing as DELETE followed by INSERT. In the former case the new tuple > will have a ctid link from the old one; in the latter case not. And > that will affect the behavior of subsequent operations. Right. The point I was driving at is - in what way will that affect the behavior of subsequent operations? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: