From: | Eildert Groeneveld <eg(at)tzv(dot)fal(dot)de> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Postmaster getting veeeery big: SUBSTR bug |
Date: | 1999-05-19 19:35:26 |
Message-ID: | 99051921401501.00833@salo.tzv.fal.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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(at)tzv(dot)fal(dot)de
=========================================
From | Date | Subject | |
---|---|---|---|
Next Message | Jens Reimann | 1999-05-19 20:24:42 | Bug report - Problems with Lotus Aproach |
Previous Message | Herouth Maoz | 1999-05-19 14:40:42 | Re: [INTERFACES] Postmaster getting veeeery big |