On Mon, May 23, 2011 at 10:20 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Aidan Van Dyk <ai...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
