| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ljb <lbayuk(at)mindspring(dot)com> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: still memory leaks with libpgtcl |
| Date: | 2002-12-28 04:14:33 |
| Message-ID: | 167.1041048873@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
ljb <lbayuk(at)mindspring(dot)com> writes:
> 3) Memory leak on connect/disconnect unfortunately is not fixed in either
> the production or beta versions. I'm seeing about 4KB loss per
> connect/disconnect.
The notes I made about this say:
2002-09-02 19:41 tgl
* src/interfaces/libpgtcl/: pgtclCmds.c, pgtclId.c: Partial
solution for 'unexpected EOF' problem with pg_disconnect: it seems
we have a choice between annoying messages and leaking memory (or
dumping core, but that's right out).
That was nearly four months ago, and so I don't recall the details,
other than that I went for the "leak memory" choice :-(
If anyone can improve the situation, step right up with a patch ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Hart | 2002-12-28 07:49:28 | libpq and multiple selects in a single query |
| Previous Message | ljb | 2002-12-28 02:59:01 | Re: still memory leaks with libpgtcl |