Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I was thinking of adding to TODO:
> * Allow shared row locks for referential integrity
> but how is that different from:
> * Implement dirty reads and use them in RI triggers
It'd be a completely different approach to solving the FK locking
problem. I wouldn't think we'd do both.
Personally I'd feel more comfortable with a shared-lock approach, if we
could work out the scalability issues. Dirty reads seem ... well ...
dirty.
regards, tom lane
