Re: Removing pgsql_tmp files

From: Michael Glaesemann <michael(dot)glaesemann(at)myyearbook(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Glaesemann <michael(dot)glaesemann(at)myyearbook(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Removing pgsql_tmp files
Date: 2010-11-08 22:00:42
Message-ID: A293F398-4BE6-4D09-8D2B-1AA406E92EF2@myyearbook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


On Nov 8, 2010, at 16:03 , Tom Lane wrote:

> Michael Glaesemann <michael(dot)glaesemann(at)myyearbook(dot)com> writes:
>> We've got over 250GB of files in a pgsql_tmp directory, some with modification timestamps going back to August 2010 when the server was last restarted.
>
> That's very peculiar. Do you keep query logs? It would be useful to
> try to correlate the temp files' PIDs and timestamps with the specific
> queries that must have created them.

We don't log all of them, but I checked those we did. It looks like it's happening when queries are timing out. I'm seeing this pattern pretty consistently:

temporary file + query
canceling statement due to statement timeout
second temp file

Here's a sample:

pid | 877
sess_id | 4ccf7257.36d
sess_line | 16
filename | pgsql_tmp877.0
accessed_at | 2010-09-15 12:14:45-04
modified_at | 2010-11-01 22:37:00-04
logged_at | 2010-11-01 22:37:01.412-04
error | LOG
sql_state | 00000
message | temporary file: path "pg_tblspc/16384/pgsql_tmp/pgsql_tmp877.0", size 87184416

pid | 877
sess_id | 4ccf7257.36d
sess_line | 17
filename | pgsql_tmp877.0
accessed_at | 2010-09-15 12:14:45-04
modified_at | 2010-11-01 22:37:00-04
logged_at | 2010-11-01 22:37:01.412-04
error | ERROR
sql_state | 57014
message | canceling statement due to statement timeout

pid | 877
sess_id | 4ccf7257.36d
sess_line | 18
filename | pgsql_tmp877.0
accessed_at | 2010-09-15 12:14:45-04
modified_at | 2010-11-01 22:37:00-04
logged_at | 2010-11-01 22:37:01.434-04
error | LOG
sql_state | 00000
message | temporary file: path "pg_tblspc/16384/pgsql_tmp/pgsql_tmp877.1", size 5480448
query |

It looks like the pgsql_tmp877.1 file is cleaned up as it doesn't appear in the pgsql_tmp directory.

> Personally, I'd not risk trying to match on PID; it should be sufficient
> to delete anything with a timestamp older than the oldest active
> backend. (Unless you've got some really long-lived sessions in
> there...)

That's easily-enough determined from pg_stat_activity.

> What PG version is this?

select version();
version
-------------------------------------------------------------------------------------------------------------------
PostgreSQL 8.4.4 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48), 64-bit
(1 row)

Michael Glaesemann
michael(dot)glaesemann(at)myyearbook(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jason Long 2010-11-08 22:42:07 Re: Full Vacuum/Reindex vs autovacuum
Previous Message Scott Marlowe 2010-11-08 21:58:34 Re: Full Vacuum/Reindex vs autovacuum

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2010-11-08 22:07:33 Re: W3C Specs: Web SQL
Previous Message Alvaro Herrera 2010-11-08 21:28:36 Re: W3C Specs: Web SQL