Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #4578: Not releaseing memory from PQmakeEmptyPGresult when calling PQisBusy - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4578: Not releaseing memory from PQmakeEmptyPGresult when calling PQisBusy
Date
Msg-id 4933.1229091313@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4578: Not releaseing memory from PQmakeEmptyPGresult when calling PQisBusy  ("Sven Almgren" <sven@blocket.se>)
List pgsql-bugs
Tree view 
"Sven Almgren" <sven@blocket.se> writes:
> ==14976== 4,480 (384 direct, 4,096 indirect) bytes in 2 blocks are
> definitely lost in loss record 19 of 55
> ==14976==    at 0x4A05809: malloc (vg_replace_malloc.c:149)
> ==14976==    by 0x38FC80E194: PQmakeEmptyPGresult (in
> /usr/lib64/libpq.so.5.1)
> ==14976==    by 0x38FC814BEC: (within /usr/lib64/libpq.so.5.1)
> ==14976==    by 0x38FC816031: (within /usr/lib64/libpq.so.5.1)
> ==14976==    by 0x38FC80D5AF: PQisBusy (in /usr/lib64/libpq.so.5.1)

AFAICS this would be your own bug, ie neglecting to collect and
eventually PQclear the result after PQisBusy has returned false.

> Without specifying too much about our system ...

If you are not willing to provide a self-contained test case there is
very little anyone else can do here.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Sven Almgren"
Date:
Subject: BUG #4578: Not releaseing memory from PQmakeEmptyPGresult when calling PQisBusy
Next
From: Zahid Khan
Date:
Subject: Re: ECPG Preprocessor throws Syntax Error [Devel Repository]