Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0ILlO013228 for ; Thu, 18 Jan 2001 16:47:24 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0ILkAJ05353; Thu, 18 Jan 2001 16:46:10 -0500 (EST) To: "Ligia M. Pimentel" cc: pgsql-sql@postgresql.org Subject: Re: Re: ltsWriteBlock: failed to write block XX of temporary file. Perharps out of disk space... In-reply-to: <944mvl$11qo$1@news.tht.net> References: <944kbb$114p$1@news.tht.net> <944mvl$11qo$1@news.tht.net> Comments: In-reply-to "Ligia M. Pimentel" message dated "Wed, 17 Jan 2001 11:59:53 -0600" Date: Thu, 18 Jan 2001 16:46:10 -0500 Message-ID: <5350.979854370@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/231 X-Sequence-Number: 899 "Ligia M. Pimentel" writes: >> I have a database and a table with 70000 records (which i dont think it's >> too much) >> I join this table with another of about the same size and put a record >> restriction (WHERE) and everything works out fine, but when I put two SUMs >> over a couple of fields and add a GROUP BY What plan does EXPLAIN show for this query? I suspect that you are causing it to sort a huge intermediate result, possibly because of insufficiently tight WHERE restrictions. >> I keep getting this error, >> >> ltsWriteBlock: failed to write block 27231 of temporary file >> Perhaps out of disk space? >> >> I checked and I have over 1GB free so I figure this must have something to >> do with configuration parameters. Well, that temp file alone is 27231*8K = 212meg, and it might be using several. So running out of disk space is not out of the question. Did you watch free space with df while the query was running? regards, tom lane