| From: | Dennis Gearon <gearond(at)cvc(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gerhard Hintermayer <g(dot)hintermayer(at)inode(dot)at>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Backend memory leakage when inserting |
| Date: | 2003-04-29 15:18:41 |
| Message-ID: | 3EAE97D1.1050000@cvc.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
a lot of people have seen JAVA leaks and ODBC leaks. Are you using those?
Tom Lane wrote:
> g(dot)hintermayer(at)inode(dot)at (Gerhard Hintermayer) writes:
>
>>I'm currently using 7.3.1 (linux 2.2.17) and noticed a memory leakage
>>in the backend when I do lots of inserts.
>
>
> Unless you provide enough info for someone else to duplicate the
> problem, it's going to be hard to say if it's been fixed or not.
>
> I see only one memory-leak patch in the CVS logs, and it's for plpgsql:
>
> 2003-03-02 15:45 tgl
>
> * src/pl/plpgsql/src/pl_exec.c (REL7_3_STABLE): Repair memory leak
> introduced by recent change to make SPI return a tupdesc even with
> zero tuples returned: some plpgsql routines assumed they didn't
> need to do SPI_freetuptable() after retrieving no tuples.
>
> This is post-7.3.2 ...
>
> regards, tom lane
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2003-04-29 15:18:48 | Re: Importing from Access 2000? |
| Previous Message | Tom Lane | 2003-04-29 15:17:48 | qsort (was Re: Solaris) |