Re: PARSE WAITING - Mailing list pgsql-performance

From Alvaro Herrera
Subject Re: PARSE WAITING
Date
Msg-id 1282612581-sup-9196@alvh.no-ip.org
Whole thread Raw
In response to Re: PARSE WAITING  (David Kerr <dmk@mr-paradox.net>)
List pgsql-performance
Excerpts from David Kerr's message of lun ago 23 18:47:02 -0400 2010:

> unlink("base/pgsql_tmp/pgsql_tmp28335.12593") = 0
> unlink("base/pgsql_tmp/pgsql_tmp28335.6041") = 0
> unlink("base/pgsql_tmp/pgsql_tmp28335.3030") = 0
> unlink("base/pgsql_tmp/pgsql_tmp28335.14737") = 0
>
> which isn't the fastest operation.. just for my info, can anyone tell me what
> pgsql_tmp is, and why the engine is wacking each file individually?

These are temp files, which you can remove without concern if the server
is down.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-performance by date:

Previous
From: David Kerr
Date:
Subject: Re: PARSE WAITING
Next
From: Jann Röder
Date:
Subject: Re: Inefficient query plan