From: Eildert Groeneveld <eg@tzv.fal.de>
To: pgsql-interfaces@postgresql.org
Subject: Postmaster getting veeeery big: SUBSTR bug
Date: Wed, 19 May 1999 21:35:26 +0200
Message-ID: <99051921401501.00833@salo.tzv.fal.de> (raw)
Never mind my initial query, it was just used for demonstration purposes.
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?
greetings
Eildert Groeneveld
=========================================
Institute for
Animal Science and Animal Behaviour
Mariensee 31535 Neustadt Germany
Tel : (49)(0)5034 871155
Fax : (49)(0)5034 92579
www : http://www.tzv.fal.de/~eg/
e-mail: eg@tzv.fal.de
=========================================
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: eg@tzv.fal.de
Subject: Re: Postmaster getting veeeery big: SUBSTR bug
In-Reply-To: <99051921401501.00833@salo.tzv.fal.de>
* 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