Received: from trends.net (root@clio.trends.ca [209.47.148.2]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA01966 for ; Fri, 4 Jun 1999 11:30:03 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by trends.net (8.8.8/8.8.8) with ESMTP id KAA00470 for ; Fri, 4 Jun 1999 10:35:45 -0400 (EDT) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA16873; Fri, 4 Jun 1999 10:33:18 -0400 (EDT) To: vikrant@chemquick.com cc: pgsql-sql@hub.org Subject: Re: [SQL] Mail about select In-reply-to: Your message of Fri, 04 Jun 1999 16:01:31 +0800 <375787DB.65CCEF22@chemquick.com> Date: Fri, 04 Jun 1999 10:33:18 -0400 Message-ID: <16871.928506798@sss.pgh.pa.us> From: Tom Lane Vikrant Rathore writes: > now i am firing a query like this: > select r.uname from radius r, radiustemp rt where r.uname<>rt.uname and > r.logdate<>rt.logdate and r.logtime<>rt.logtime; > After some time i get response > "Segmentation Error" > core(sumped) How big are your tables? That query will probably produce an output row for almost every combination of a row from radius with a row from radiustemp, which might overflow the allowed memory for your application. I suppose what you really want is to find the rows in radius that do not have duplicates in radiustemp, but that query won't do it... regards, tom lane