Tom Lane <[EMAIL PROTECTED]> wrote:
> Surely this'd require having those transactions display exactly what
> their current oldest-xmin is. We've talked about that before, and it
> seems a good idea, but it requires a bit more infrastructure than is
> there now --- we'd need some snapshot-management code that could keep
> track of all live snapshots within each backend.
I see. I'll need to avoid long transactions during heavily updates.
The additonal management seems to be good, but not so easy
because we should not lead lock contentions at the same time.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
