From: | ROBERT KLAUS <rklaus0712(at)wowway(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | cleanup of pgsql_tmp directory |
Date: | 2013-02-05 17:52:36 |
Message-ID: | 1718178017.1392980.1360086756170.JavaMail.root@md06.wow.synacor.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Updating: I found two other sessions running the same query. Once I killed them the pg_tmp files were automatically deleted.
>>
This morning we found out that our filesystem was at 98% and filling quickly. We immediately found one query running for a long time and saw 1500+ files in the pgsql_tmp directory we could attribute to it.
I killed using pg_terminate_backend and some space was reclaimed, but the temporary files from the process are still in the pgsql_tmp directory.
We're on postgres 8.4.9 on centos. Which process should be deleting these files and what is normally the delay? I'm assuming the postmaster process will eventually delete them, but does the server have to be bounced in order for this to happen? It's been 30 minutes since the process was killed.
Also, is there some method of governing the temporary space used? Our temp_tablespace parameter is null.
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-02-05 18:06:38 | Re: cleanup of pgsql_tmp directory |
Previous Message | Moshe Jacobson | 2013-02-05 17:34:47 | Re: Passing dynamic parameters to a table-returning function |