Received: from jupiter.tzv.fal.de (jupiter.tzv.fal.de [192.108.34.1])
	by hub.org (8.9.3/8.9.3) with ESMTP id FAA07093
	for <pgsql-interfaces@postgresql.org>;
	Tue, 18 May 1999 05:21:04 -0400 (EDT)
	(envelope-from eg@salo.tzv.fal.de)
Received: from salo.tzv.fal.de (eg@salo [192.108.34.39]) by jupiter.tzv.fal.de
	(8.8.5/8.7.3) with ESMTP id LAA07238 for
	<pgsql-interfaces@postgresql.org>;
	Tue, 18 May 1999 11:20:56 +0200 (MET DST)
Received: from [[UNIX: localhost]] ([[UNIX: localhost]])
	by salo.tzv.fal.de (8.8.7/8.8.7) id LAA01105
	for pgsql-interfaces@postgresql.org; Tue, 18 May 1999 11:20:56 +0200
From: Eildert Groeneveld <eg@tzv.fal.de>
Reply-To: eg@tzv.fal.de
Organization: FAL
To: pgsql-interfaces@postgresql.org
Subject: Postmaster getting veeeery big
Date: Tue, 18 May 1999 11:05:45 +0200
X-Mailer: KMail [version 1.0.21]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99051811205503.00540@salo.tzv.fal.de>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id FAA07101

Hello everyone,
we observe a problem when doing some sort of aggregation like

select distinct count(substr(narodene,5,4)) from raw_field;

(raw_field has 1300000 rows)


On executing this query the postmaster grows in memory size until it runs
out of virtual mem and dies.

Any ideas of what is going on and how to avoid this?

Eildert Groeneveld
ps. RedHat5.2 postgresql-6.4.2-4  
=========================================
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
=========================================