log_temp_files (integer), tuning work_mem - Mailing list pgsql-performance

From Tory M Blue
Subject log_temp_files (integer), tuning work_mem
Date
Msg-id CAEaSS0Z7xq_gXnF0GtSG+cjjYKBbzpmX3XVHCSQGOQ2rUYAsAA@mail.gmail.com
Whole thread Raw
Responses Re: log_temp_files (integer), tuning work_mem  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgsql-performance
log_temp_files (integer)
Controls logging of temporary file names and sizes. Temporary files can be created for sorts, hashes, and temporary query results. A log entry is made for each temporary file when it is deleted. A value of zero logs all temporary file information

so I've set this to;

log_temp_files = 0                      # log temporary files equal or larger

Reloaded the config and still have not seen a creation or deletion of a log file. Is this still valid in 9.3 and do I need to change anything else?

I've got duration queries spitting out;

2014-11-05 12:11:32 PST rvtempdb postgres [local] 31338 2014-11-05 12:11:32.257 PSTLOG:  duration: 1609.707 ms  statement: COPY adgroups (adgroup_id, name, status, campaign_id, create_date, modify_date) FROM stdin;

So logging is working.

I'm set to info ;

log_min_messages = info   

So what would be the cause of not seeing anything ,and how can one turn work_mem without seeing these entries?

Thanks!
Tory


pgsql-performance by date:

Previous
From: Tory M Blue
Date:
Subject: Re: 9.3 performance issues, lots of bind and parse log entries
Next
From: Artūras Lapinskas
Date:
Subject: Index order ignored after `is null` in query