On Thu, 7 Oct 2004, Oliver Jowett wrote:
Probably the next question is, do we want a database-side timeout on how long prepared txns can stay alive before being summarily rolled back?
That sounds very dangerous to me. You could end up breaking global atomicity if some other resource in the global transaction committed.
The transaction monitor can do timeouts if necessary, and a super user has to resolve the in-doubt transactions if the TM crashes non-recoverably.
- Heikki
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
