From: Tom Lane <tgl@sss.pgh.pa.us>
To: eg@tzv.fal.de
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Postmaster getting veeeery big: SUBSTR bug
Date: Wed, 19 May 1999 16:29:04 -0400
Message-ID: <954.927145744@sss.pgh.pa.us> (raw)
In-Reply-To: <99051921401501.00833@salo.tzv.fal.de>
Eildert Groeneveld <eg@tzv.fal.de> writes:
> Herouth was right in stating: "memory used for substr function" has to be
> the real cause of the problem because any substr select exhibits this
> behaviour:
> select substr(tets,1,2) from raw_field;
> This one starts the postmaster at around 3MB and finishes at 40.
> Unfortunately, I have no idea about C, can someone identify the problem
> and come up with a patch?
The problem is well known and is on the TO-DO list: memory consumed
while evaluating expressions is not reclaimed until end of statement.
It's by no means specific to substr().
Unfortunately, fixing it is not a small amount of work (else it'd have
been done already). I'm hoping to see it fixed in 6.6.
regards, tom lane
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-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, eg@tzv.fal.de
Subject: Re: [INTERFACES] Postmaster getting veeeery big: SUBSTR bug
In-Reply-To: <954.927145744@sss.pgh.pa.us>
* 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