Re: Memory growth observed with C++ application consuming libpq.dll on Windows

We did run our application under valgrind on Linux. We did not see any
leaks. There is no platform dependent code in our application. We are
seeing gradual memory growth only on windows.

That is what lead me to believe the leak may be present in postgresql. I
will run under available memory tools on windows and get back to you.

I will also try to create a sample and see if I can reproduce the problem.

Thanks,
Rajesh

On Fri, 2 Aug 2024, 21:45 Ranier Vilela, <ranier(dot)vf(at)gmail(dot)com> wrote:

> Em sex., 2 de ago. de 2024 às 11:54, Rajesh Kokkonda <
> rajeshk(dot)kokkonda(at)gmail(dot)com> escreveu:
>
>> Okay. I will try to create one sample program and send it to you sometime
>> next week. In the meantime, I am listing down all the methods we are
>> consuming from libpq.
>>
>> PQconnectdbParams
>> PQstatus
>> PQerrorMessage
>> PQpingParams
>> PQfinish
>> PQresultStatus
>> PQclear
>> PQsetSingleRowMode
>> PQntuples
>> PQnfields
>> PQftype
>> PQgetvalue
>> PQgetlength
>> PQgetisnull
>> PQgetCancel
>> PQfreeCancel
>> PQcancel
>> PQsetErrorVerbosity
>> PQsendPrepare
>> PQsendQueryPrepared
>> PQgetResult
>> PQconsumeInput
>> PQisBusy
>> PQsetnonblocking
>> PQflush
>> PQsocket
>> PQtransactionStatus
>> PQresultErrorField
>>
>> It is highly likely that the memory consumption is caused by your
> application.
> Perhaps due to the lack of freeing up the resources used by the library.
> You can try using this tool, to find out the root cause.
>
> https://drmemory.org/
>
> best regards,
> Ranier Vilela
>