I changed the DSN to Postgres and tested locally. I added another sleep before the loop and ran lsof there as well, then compared the outputs. There were many files open at the end of the program not present in the first list, but none of them seem to be a leaked database handle: 
11116432.pl    17198 choroba  mem    REG  254,0   118512  6711636 /usr
+/lib64/libsasl2.so.3.0.0
11116432.pl    17198 choroba  mem    REG  254,0    14648  6711746 /usr
+/lib64/libkeyutils.so.1.6
11116432.pl    17198 choroba  mem    REG  254,0    14720  6719925 /usr
+/lib64/libcom_err.so.2.1
11116432.pl    17198 choroba  mem    REG  254,0   159456  5909809 /lib
+64/libselinux.so.1
11116432.pl    17198 choroba  mem    REG  254,0   199576  6714342 /usr
+/lib64/libk5crypto.so.3.1
11116432.pl    17198 choroba  mem    REG  254,0   217032   264891 /var
+/lib/nscd/passwd
11116432.pl    17198 choroba  mem    REG  254,0  2681240  6719579 /usr
+/lib64/libcrypto.so.1.1
11116432.pl    17198 choroba  mem    REG  254,0   299128  6729817 /usr
+/lib64/libpq.so.5.10
11116432.pl    17198 choroba  mem    REG  254,0   309784  6714338 /usr
+/lib64/libgssapi_krb5.so.2.2
11116432.pl    17198 choroba  mem    REG  254,0   335416  6715270 /usr
+/lib64/libldap_r-2.4.so.2.10.9
11116432.pl    17198 choroba  mem    REG  254,0   442648  6730433 /usr
+/lib64/libssl.so.1.1
11116432.pl    17198 choroba  mem    REG  254,0    52440  6714354 /usr
+/lib64/libkrb5support.so.0.1
11116432.pl    17198 choroba  mem    REG  254,0   575808  6711541 /usr
+/lib64/libpcre.so.1.2.9
11116432.pl    17198 choroba  mem    REG  254,0    60472  6715268 /usr
+/lib64/liblber-2.4.so.2.10.9
11116432.pl    17198 choroba  mem    REG  254,0   900864  6714352 /usr
+/lib64/libkrb5.so.3.3
11116432.pl    17198 choroba  mem    REG  254,0    92216  5909835 /lib
+64/libz.so.1.2.11
11116432.pl    17198 choroba  mem    REG  254,0    96624  5909861 /lib
+64/libresolv-2.26.so
11116432.pl    17198 choroba  mem    REG  254,2   844776 14710922 /hom
+e/choroba/perl5/lib/perl5/x86_64-linux-thread-multi/auto/DBD/Pg/Pg.so

[download]

It seems to be an Oracle issue, see File Handles Staying Open on ocius.msb (they're using C++, so it doesn't seem to be Perl related).

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

In reply to Re^3: FD leaks while interacting with DB by choroba
in thread FD leaks while interacting with DB by prabakar.bhatt

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.