All kinds of evil things may happen when you fork with an open database connection.

What (if anything) happens depends on the database system, what you do to the connection after forking, ...

I don't have the answer to what happens in your case

The problem is that the database system is not prepared to have several process share the same connection - the purpose of the connection is to give a single channel of access, when that is shared evereything might break.

Neither the DBI or the database systems are 'fork-safe'. The DBI is not really threadsafe yet. Most DBD-drivers are definitely not thread safe.

So avoid forking when you have an active database connection.

In reply to Re: Is DBI trapping CHLD sigs, is there a workaround? by htoug
in thread Is DBI trapping CHLD sigs, is there a workaround? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.