On Thu, Dec 11, 2008 at 10:09:40PM +0500, Ahmed Shinwari wrote:
> through ECPG preprocessor which I think are potential bugs;
>
> 1- I get this error message from preprocessor,
>
> *ERROR: cursor "m_name_cursor" already defined *
>
> Below is the code snippet, error message is thrown on the last
The following bug has been logged online:
Bug reference: 4578
Logged by: Sven Almgren
Email address: s...@blocket.se
PostgreSQL version: 8.3.5
Operating system: CentOS release 5.2 (Final)
Description:Not releaseing memory from PQmakeEmptyPGresult when
calling PQisBusy
"Sven Almgren" 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 0
>I might be missing something here, but where do you see the bug? The cursor is
>indeed already defined.
What i understand here is,we should be able to DECLARE cursor again
with the same name if that is CLOSE already.
--- On Fri, 12/12/08, Michael Meskes wrote:
From: Michael Meskes
Subject:
Zahid Khan writes:
>> I might be missing something here, but where do you see the bug? The cursor
>> is
>> indeed already defined.
> What i understand here is,we should be able to DECLARE cursor again
> with the same name if that is CLOSE already.
No, CLOSE reverses the effect of OPEN, not of
