On Tue, Apr 7, 2015 at 7:16 PM, Qingqing Zhou <zhouqq.postgres@gmail.com> wrote:
> If another transaction T2 coming later than T1, and if we prune early,
> then T1 can suddenly hang on insertion waiting for T2 to complete. But
> does this violate any isolation rule?
Well, it means that you don't lock a row that you delete (and values
that appeared in that row if they're constrained by a unique index)
just because you happened to also insert that row. That would probably
break client code.
--
Peter Geoghegan