| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Nestor A(dot) Diaz" <nestor(at)tiendalinux(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pgsql_tmp consuming all inodes |
| Date: | 2014-11-21 15:15:06 |
| Message-ID: | 6039.1416582906@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Nestor A. Diaz" <nestor(at)tiendalinux(dot)com> writes:
> As you can see from above it creates a lots of temp files for the same
> query.
> And finally the query is this:
Could we see what EXPLAIN says about that?
You might try EXPLAIN ANALYZE too, but we're expecting that to run out
of disk space :-(.
I'm speculating wildly here, but I wonder whether it still runs
out of disk space if you remove the COALESCE((SELECT...)) output
expression.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-11-21 15:21:28 | Re: pgsql_tmp consuming all inodes |
| Previous Message | Bill Moran | 2014-11-21 15:10:08 | Re: pgsql_tmp consuming all inodes |