| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Fernando Papa" <fpapa(at)claxson(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: tuplestore: write failed |
| Date: | 2002-10-17 03:36:01 |
| Message-ID: | 5488.1034825761@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Fernando Papa" <fpapa(at)claxson(dot)com> writes:
> In server's logfile I found this:
> 2002-10-16 11:53:25 ERROR: tuplestore: write failed
> I run again the query an I get the same error.
> I check the disk space... everithing ok.
Disk space overrun would certainly be the most probable explanation.
Checking free space *after* the failure proves nothing at all, because
the temp files would have been released on failure. You might try
running "df" at frequent intervals while the query is running to confirm
my guess that it's exhausting disk space.
As for *why* it's exhausting disk space, maybe you are doing an
unconstrained join between two large tables? It's hard to guess when
you did not show us the failing query nor the schemas for the tables
it uses.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-17 03:52:38 | Re: signals?? |
| Previous Message | Brett Elliott | 2002-10-17 03:30:29 | Re: transactions |