If the caller is buggy and has statement handles still open, they can
still "work" even if we have thrown away the db handle.
Where, after forking, "work" means "use the same connection in
multiple processes simultaneously, without locking". This could
result in arbitrary crazy nbehaviour (eg, TLS crypto failures).
No functional change with existing callers since they don't have this
bug.
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
# db is reopened in each child.
$whoami = $set_whoami;
+ $dbh_tests->disconnect();
undef $dbh_tests;
foreach my $task (@$tasks) {