| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel query and temp_file_limit |
| Date: | 2016-05-17 20:53:40 |
| Message-ID: | CAA4eK1LLeq7JTON=kFjAXZauM3zm9Ck=iTaUU0_H5oj=DPbUUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 18, 2016 at 12:55 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>
> temp_file_limit "specifies the maximum amount of disk space that a
> session can use for temporary files, such as sort and hash temporary
> files", according to the documentation. That's not true when parallel
> query is in use, since the global variable temporary_files_size
> receives no special treatment for parallel query.
>
What kind of special treatment are you expecting for temporary_files_size,
also why do you think it is required? Currently neither we build hash in
parallel nor there is any form of parallel sort work.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manuel Kniep | 2016-05-17 21:00:14 | foreign table batch inserts |
| Previous Message | Joshua D. Drake | 2016-05-17 20:34:51 | Re: Reviewing freeze map code |