From: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
To: Maurice Gittens <mgittens@gits.nl>
Cc: Massimo Dal Zotto <dz@cs.unitn.it>
Cc: Pgsql Development <hackers@postgresql.org>
Cc: David Gould <dg@illustra.com>
Subject: Re: [HACKERS] Everything leaks; How it mm suppose to work?
Date: Thu, 09 Apr 1998 13:00:24 +0000
Message-ID: <352CC668.134F4FE7@alumni.caltech.edu> (raw)
References: <00d901bd63a6$a9bd0520$fcf3b2c2@caleb..gits.nl>
> >Does it make sense to have a 'row' context which is released just
> >before starting with a new tuple ? The total number or free is the
> >same but they are distributed over the query and unused memory should
> >not accumulate.
> >I have seen backends growing to 40-60MB with queries which scan a
> >very large number of rows.
> I think this would be appropiate.
It seems that the CPU overhead on all queries would increase trying to
deallocate/reuse memory during the query. There are lots of places in
the backend where memory is palloc'd and then left lying around after
use; I had assumed it was sort-of-intentional to avoid having extra
cleanup overhead during a query.
- Tom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: lockhart@alumni.caltech.edu, mgittens@gits.nl, dz@cs.unitn.it, hackers@postgresql.org, dg@illustra.com
Subject: Re: [HACKERS] Everything leaks; How it mm suppose to work?
In-Reply-To: <352CC668.134F4FE7@alumni.caltech.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox