Skip site navigation (1) Skip section navigation (2)

Postmaster getting veeeery big: SUBSTR bug

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: (view raw, whole thread or download thread mbox)
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

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?


Eildert Groeneveld
Institute for
Animal Science and Animal Behaviour
Mariensee 31535 Neustadt Germany
Tel   : (49)(0)5034 871155
Fax   : (49)(0)5034 92579
www   : 
e-mail: eg(at)tzv(dot)fal(dot)de

pgsql-interfaces by date

Next:From: Jens ReimannDate: 1999-05-19 20:24:42
Subject: Bug report - Problems with Lotus Aproach
Previous:From: Herouth MaozDate: 1999-05-19 14:40:42
Subject: Re: [INTERFACES] Postmaster getting veeeery big

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group