> Kohei KaiGai wrote: > I'm not clear the reason why the argument of > CheckForSerializableConflictIn() was changed from the one in > heap_insert(). The code was probably just based on heap_insert() before this recent commit: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=9d306c66e63eb7f45eab9475b3f96c3134bacac6 > Is it feasible that newly inserted tuples conflict with existing > tuple locks when we expand insert to support multiple tuples at > once? No. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
