typical query produced from this product (I didn't write the piece that
creates the queries, and I know that the queries could definitely be
optimized):

 SELECT cms_users.usr_id 
 FROM cms_usr_prof, cms_usr_incenvalue, cms_opt_in, cms_users,
cms_usr_prodvalue
 WHERE (((cms_usr_prof.cluster_id2=2) OR (cms_usr_prof.cluster_id2=7))
 OR ((cms_usr_incenvalue.incenvalue_id=283 AND cms_usr_prodvalue.num_sol >
0) OR (cms_usr_incenvalue.incenvalue_id=283 AND cms_usr_prodvalue.num_resp >
0))
 OR (cms_usr_prof.last_visit_dt< (now() - 3)::datetime AND
cms_usr_prof.last_visit_dt >= (now() - 4)::datetime)
 OR (cms_opt_in.optin_creation_date>= (now() - 14)::datetime)
 OR (cms_usr_prof.sum_resp_time/cms_usr_prof.total_unq_resp >= 2 AND
cms_usr_prof.sum_resp_time/cms_usr_prof.total_unq_resp < 3 AND
cms_usr_prof.total_unq_resp > 0)
 OR (cms_users.usr_age>=21 AND cms_users.usr_age<=25)
 OR ((cms_users.usr_bmonth=1) OR (cms_users.usr_bmonth=2) OR
(cms_users.usr_bmonth=3) OR (cms_users.usr_bmonth=4) OR
(cms_users.usr_bmonth=5) OR (cms_users.usr_bmonth=6) OR
(cms_users.usr_bmonth=7) OR (cms_users.usr_bmonth=8) OR
(cms_users.usr_bmonth=9) OR (cms_users.usr_bmonth=10) OR
(cms_users.usr_bmonth=11) OR (cms_users.usr_bmonth=12))
 OR (cms_users.usr_gender=-1)
 OR (cms_users.usr_suffix='COM'))
 OR (   (cms_users.usr_id=cms_opt_in.usr_id  AND  cms_opt_in.optin_id=1 AND
cms_opt_in.drq_choice=101 AND  cms_opt_in.optin_sub=1 )
 OR    (cms_users.usr_id=cms_opt_in.usr_id  AND  cms_opt_in.optin_id=3 AND
cms_opt_in.drq_choice=103 AND  cms_opt_in.optin_sub=1 )
 OR    (cms_users.usr_id=cms_opt_in.usr_id  AND  cms_opt_in.optin_id=3 AND
cms_opt_in.drq_choice=105 AND  cms_opt_in.optin_sub=1 )
 OR    (cms_users.usr_id=cms_opt_in.usr_id  AND  cms_opt_in.optin_id=4 AND
cms_opt_in.drq_choice=107 AND  cms_opt_in.optin_sub=1 )
 OR    (cms_users.usr_id=cms_opt_in.usr_id  AND  cms_opt_in.optin_id=5 AND
cms_opt_in.drq_choice=111 AND  cms_opt_in.optin_sub=1 ))
 AND (cms_users.usr_id=cms_usr_prof.usr_id)
 AND (cms_users.usr_id= cms_usr_incenvalue.usr_id)
 AND (cms_users.usr_id= cms_opt_in.usr_id)
 AND  usr_glob_sub=1


-----Original Message-----
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 11, 2000 6:21 PM
To: Bruce Momjian
Cc: Gregory Krasnow; [EMAIL PROTECTED]
Subject: Re: [GENERAL] backend running out of memory in v7.0 


Bruce Momjian <[EMAIL PROTECTED]> writes:
>> stack size (kbytes)         8192
>                              ^^^^

> I bet this is the problem.

Nah, 8 meg stack should be fine --- that's the same configuration I run.

>> On Thu, 11 May 2000, Gregory Krasnow wrote:
>>>> I know that there were some issues with many AND/OR joins in
>>>> PostgreSQL 6.5 which caused the backend process to run out of memory.  
>>>> I am still having some similar issues in PostgreSQL 7.0.

AFAIK the AND/OR issues are largely licked, but we do still have
problems with memory leakages during execution for expressions involving
pass-by-reference datatypes.  There are plans on the table to fix that
for 7.1.

But, that might or might not be your problem.  It's difficult to give
any advice without some details about the queries that are giving you
trouble.

                        regards, tom lane

Reply via email to