pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Andrews <pete@piedmontdata.com>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] runaway backend process
Date: Fri, 10 Sep 1999 10:45:14 -0400
Message-ID: <10210.936974714@sss.pgh.pa.us> (raw)
In-Reply-To: <37D8C13A.53DC5B8B@piedmontdata.com>

Peter Andrews <pete@piedmontdata.com> writes:
> 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?

Do you see the same sort of behavior if you just "explain" the query
without actually executing it?  If so, it's a planner problem.

I recently identified a flaw in cnfify() that causes it to use an amount
of space exponential in the number of AND/OR terms.  There is a fix in
the current CVS sources, but I'm hesitant to commit it into REL6_5 since
it's not well tested yet.  If you want, you can try dropping
src/backend/optimizer/prep/prepqual.c from a current snapshot into
the 6.5 code (probably be easiest to work from the latest 6.5.2 beta,
rather than 6.5.1).

			regards, tom lane



view thread (3+ messages)

Message-ID: <10210.936974714@sss.pgh.pa.us>
Permalink:  ../10210.936974714@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10210.936974714@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, pete@piedmontdata.com
  Subject: Re: [SQL] runaway backend process
  In-Reply-To: <10210.936974714@sss.pgh.pa.us>
  References: <37D8C13A.53DC5B8B@piedmontdata.com> <10210.936974714@sss.pgh.pa.us>

* 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