pgsql-server/src/interfaces/libpgtcl pgtclId.c

pgsql-server/src/interfaces/libpgtcl pgtclId.c

Post by Tom La » Sun, 02 Feb 2003 11:11:36



CVSROOT:        /cvsroot
Module name:    pgsql-server

Modified files:
        src/interfaces/libpgtcl: pgtclId.c

Log message:
        Prevent core dump from calling Tcl_DontCallWhenDeleted() with a null
        interp pointer.  Per report from Gerhard Hintermayer.

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

 
 
 

pgsql-server/src/interfaces/libpgtcl pgtclId.c

Post by Tom La » Sun, 02 Feb 2003 11:12:44


CVSROOT:        /cvsroot
Module name:    pgsql-server

Modified files:
        src/interfaces/libpgtcl: pgtclId.c

Log message:
        Apply ljb's patch to prevent both memory leak and core dump during
        connection shutdown.  This is a grotty workaround for a Tcl bug, but
        said bug has been there long enough that I'm not holding my breath
        for a real fix.  Per discussions and testing from ljb and g.hintermayer.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate

message can get through to the mailing list cleanly

 
 
 

1. pgsql-server/src/interfaces/libpgtcl pgtclId.c

CVSROOT:        /cvsroot
Module name:    pgsql-server

Modified files:
        src/interfaces/libpgtcl: pgtclId.c

Log message:
        Obviously noone has ever tested the doubling of availiable result ids
        up to
        reaching the hard limit. After opening 16(=current REST_START value)
        results via pg_exec, the next pg_exec tries to find an empty slot
        forever :-( . In PgSetResultId file pgtclId.c in the for loop there
        has to be done a break, if res_max ist reached. The piece of code
        should look like
        if (resid == connid->res_max)
        {
        resid = 0;
        break;   /* the break as to be added */
        }

        now everything works (double available results after reaching
        RES_START up to reaching RES_HARD_MAX)

        Gerhard Hintermayer

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

2. Bug in SQL 7 OLE DB Provider?

3. Why can't 2 datalist controls be on 1 form

4. pgsql-server/src/interfaces/libpgtcl pgtclCmds ...

5. SURVEY: Skills Management in IT

6. Oracle 8.1.6 on Solaris or Linux?

7. pgsql-server/src/interfaces/libpgtcl pgtclCmds.c

8. pgsql-server/src/interfaces/libpq pqsignal.c

9. pgsql-server/src/interfaces/libpq fe-connect.c

10. pgsql-server/src/interfaces/libpq fe-secure.c

11. pgsql-server/src/interfaces/libpq fe-connect.c