Follow-up to r3756: make the !ConnectionPool really thread-safe by tracking in the !PooledConnection instance the thread which created it. Should fix #3504.
Authored by: cboos 2006-09-22
Parent: [r3762]
Child: [r3764]
