Trying to share the database handle between two processes like you are doing is just asking for trouble. The best solution would be to connect to the database after the fork, or at least have the child process reconnect to the database after the fork.

You also need to read up on what happens when the process forks, because with the example code you have posted, the next step after the fork is that both the parent and child process are going to attempt to drop the 'foo' table, and then they are both going to call waitpid, and then both attempt to disconnect from the database.

www.jasonkohles.com
We're not surrounded, we're in a target-rich environment!

In reply to Re: DBI handler after perfoming fork? by jasonk
in thread DBI handler after perfoming fork? by AV-2

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.