From: | Yasir <yasir(dot)hussain(dot)shah(at)gmail(dot)com> |
---|---|
To: | Rajesh Kokkonda <rajeshk(dot)kokkonda(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Memory growth observed with C++ application consuming libpq.dll on Windows |
Date: | 2024-08-01 11:57:04 |
Message-ID: | CAA9OW9fo38Fi31vPN8YDxo43kwpaUjupB+mV-tA+Mtf9nNf0hA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Rajesh,
Can you please attach a sample code snippet showing libpq's functions being
called? It will help to identify the libpq's functions to investigate
further for a potential mem leak.
Regards...
Yasir Hussain
On Thu, Aug 1, 2024 at 4:30 PM Rajesh Kokkonda <rajeshk(dot)kokkonda(at)gmail(dot)com>
wrote:
> Hi,
>
> We are seeing a gradual growth in the memory consumption of our process on
> Windows. Ours is a C++ application that directly loads libpq.dll and
> handles the queries and functions. We use setSingleRowMethod to limit the
> number of rows returned simultaneously to the application. We do not
> observe any memory increase when the application is run on Linux. There is
> no code difference between Windows and Linux from the
> application standpoint. We ran valgrind against our application on Linux
> and found no memory leaks. Since the same code is being used on Windows as
> well, we do not suspect any memory leak there. The question is if there
> are any known memory leaks with the version of the library we are using on
> Windows. Kindly let us know.
>
> The version of the library on Linux is libpq.so.5.16
>
> The windows version of the library is 16.0.3.0
>
>
> [image: image.png]
>
> Thanks,
> Rajesh
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-08-01 11:57:05 | Re: can we mark upper/lower/textlike functions leakproof? |
Previous Message | Amit Kapila | 2024-08-01 11:53:16 | Re: Conflict detection and logging in logical replication |