Robert Lor wrote: > Robert Treat wrote: > > On Wednesday 04 June 2008 22:04:54 Greg Smith wrote: > > > >> I was just talking to someone today about building a monitoring tool for > >> this. Not having a clear way to recommend people monitor use of work_mem > >> and its brother spilled to disk sorts is an issue right now, I'll whack > >> that one myself if someone doesn't beat me to it before I get time. > >> > > > > I remember *years* ago, someone wrote a perl script to poll pgsql_tmp and > > print out anytime something showed up... you could probably find that in > > the > > archives if you look around. > > > > of course to me this sounds like an excellent idea for a dtrace probe ;-) > > > > > > Actually, you can find out from the sort-end probe now whether or not > the sort spilled to disk and number of disk blocks used. This is one of > the probes from Simon. > > TRACE_POSTGRESQL_SORT_END(state->tapeset, > (state->tapeset ? > LogicalTapeSetBlocks(state->tapeset) : > (state->allowedMem - state->availMem + 1023) / > 1024));
8.3 has GUC log_temp_files. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
