Re: [GENERAL] huge backend processes

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Jim Mercer <jim(at)reptiles(dot)org>
Cc: pgsql-general(at)postgreSQL(dot)org
Subject: Re: [GENERAL] huge backend processes
Date: 1999-08-18 20:24:20
Message-ID: 199908182024.QAA08851@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> maybe i'm doing something wrong here:
>
> CREATE TABLE samples
> (
> mark abstime,
> subnet inet,
> bytes_in float8,
> bytes_out float8
> );
> CREATE INDEX samples_mark ON samples (mark);
>
> --- fill it with lots and lots of data
>
> BEGIN WORK;
> DECLARE mycurs CURSOR FOR
> SELECT DATE_PART('epoch', mark), subnet, bytes_in, bytes_out

This is clearly a known problem. We need a per-tuple memory context.
Function calls that return palloc'ed memory is not freed for each tuple.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Hub.Org News Admin 1999-08-19 12:13:33
Previous Message Jim Mercer 1999-08-18 19:31:41 Re: [GENERAL] huge backend processes