From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sasmit Utkarsh <utkarshsasmit(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Assitance needed for the resolution of memory leak |
Date: | 2023-10-11 20:37:15 |
Message-ID: | 881280.1697056635@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sasmit Utkarsh <utkarshsasmit(at)gmail(dot)com> writes:
> Like for an ex: I have provided the test run for a file which has 4
> duplicate entries in the input file and below is the leak reported. I have
> followed
> consistently using PQclear to free all PGresult objects.
No you haven't: you've got two PQexec-something calls and
only one PQclear. If control reaches here:
> res = PQexec(conn, Command);
that will overwrite your only pointer to the PQexecParams
result, and you won't clear it.
BTW, if this is what your code actually looks like in your editor,
it's no wonder you can't follow its basic control flow. Indent
according to the brace structure, and your life will get easier.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sasmit Utkarsh | 2023-10-11 21:19:12 | Re: Assitance needed for the resolution of memory leak |
Previous Message | Sasmit Utkarsh | 2023-10-11 20:26:20 | Re: Assitance needed for the resolution of memory leak |