> That's the behaviour I wanted to get from it. RI triggers
> need to see what's committed and what their own transaction
> did so far. That's HeapTupleSatisfiesNow().
>
> Since they lock everything they access, they simply force the
> old (pre MVCC) behaviour - wait if something is actually in
> use until the other transaction ends. No snapshots, no pain.
Sounds good.
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
