| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | andreas(dot)papst(at)univie(dot)ac(dot)at, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #13974: temp_file_limit effects vacuum |
| Date: | 2016-02-19 20:04:25 |
| Message-ID: | 26461.1455912265@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> andreas(dot)papst(at)univie(dot)ac(dot)at wrote:
>> I'm pretty sure, it works as intended, but maybe it is useful to other
>> postgres users too to have stated in the description of
>> temp_file_limit
>> that this value effects vacuum runs too:
>> vacuumdb: vacuuming of database "test" failed: ERROR: temporary file
>> size exceeds temp_file_limit (2097152kB)
> This seems like a bug to me.
I don't know what vacuum would be doing that would involve creating
temp files at all. Seems like we need more information here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-02-19 21:45:55 | Re: BUG #13970: Vacuum hangs on particular table; cannot be terminated - requires `kill -QUIT pid` |
| Previous Message | jaime soler | 2016-02-19 16:56:43 | Re: BUG #13969: PostgreSQL 9.5.0-1 no longer available from apt.postgresql.org |