> If anyone sees this, it's because the postgres DBD object went out of > scope and was disconnected underneath me (the script forks). > > The fix was to simply use the "InactiveDestory => 1" as an option at > the time of dbconnect() as per the doc. Wow, that was painful.
Glad it got solved! I didn't reply as I couldn't figure out what was going on, but in retrospect forking is always a good suspect for mysterious DBI issues (similar to the way SELinux is for mysterious Linux issues :) -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8
signature.asc
Description: PGP signature
