| From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
|---|---|
| To: | Rajesh Kokkonda <rajeshk(dot)kokkonda(at)gmail(dot)com> |
| Cc: | Yasir <yasir(dot)hussain(dot)shah(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Memory growth observed with C++ application consuming libpq.dll on Windows |
| Date: | 2024-08-02 16:15:07 |
| Message-ID: | CAEudQAqeVbJi9wWXKOyk6v2NNa3CC=6aPbe3=2JkAXjtZWS90A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
best regards,
Ranier Vilela
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2024-08-02 16:22:36 | Re: can we mark upper/lower/textlike functions leakproof? |
| Previous Message | Joe Conway | 2024-08-02 16:13:31 | Re: can we mark upper/lower/textlike functions leakproof? |