From: Peter Andrews <pete@piedmontdata.com>
To: pgsql-sql@postgresql.org
Subject: runaway backend process
Date: Fri, 10 Sep 1999 04:28:43 -0400
Message-ID: <37D8C13A.53DC5B8B@piedmontdata.com> (raw)
Any help with this problem would be greatly appreciated. After
executing the following query, the postgres backend server process that
is executing the query grows in size until it consumes well over 200 MB
and takes several minutes to finish:
select mlno from table where
(area='01' and sub_area='01') or
(area='01' and sub_area='02') or
(area='01' and sub_area='03') or
(area='01' and sub_area='04') or
(area='07' and sub_area='01') or
(area='07' and sub_area='02') or
(area='07' and sub_area='03') or
(area='08' and sub_area='01') or
(area='08' and sub_area='03') or
(area='09' and sub_area='01') or
(area='09' and sub_area='02') or
(area='04') or
(area='05') or
(area='06') or
(area='99');
A similar query with fewer terms does not cause an abnormal increase in
backend process size, and executes in under a second. Does anyone have
any suggestions as to what might be causing this behavior?
Redhat 5.2
PostgreSQL 6.5.1
196MB RAM
database has been vacuum analyzed
table contains ~ 10000 rows
Peter Andrews
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: pete@piedmontdata.com
Subject: Re: runaway backend process
In-Reply-To: <37D8C13A.53DC5B8B@piedmontdata.com>
References: <37D8C13A.53DC5B8B@piedmontdata.com>
* 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