Honestly my best advice? Create a short stand alone script that can duplicate it.
Create a temporary table, populate it, query it over and over again, and demonstrate the memory leak. With a clear test case, you're more likely to motivate someone to fix it. On Sat, Nov 1, 2014 at 5:20 PM, Krystian Samp <[email protected]> wrote: > Hello DBD-Pg! > > I've been struggling now for a few days with leaking memory in my long > running Perl script. Step by step I narrowed the source of the leak. And it > turned out to be the fetching of array ( text[] ) column from a postgresql > db. I tried: using fetchall_hashref( {} ), other variations of fetchall, all > variations of fetchrow_*, prepare vs prepare_cached, prepare+fetch_* vs > selectall_*. The result is always the same. If I remove the array column > from SELECT then the memory leak goes away. I detect the memory leak with > Devel::Monitor by comparing number of new SVs before and after the queries - > and I do it multiple times which shows that this number is only increasing > over time. > > I found few thread on the internet reporting some leaks related to > fetchall_* etc. but these didn't suggest any working solution. > > Is this a known problem? Am I doing something wrong? Would you have advice > how to fix it? > > Thank you in advance, > Kris
