This is a discussion on Re: Advice on selecting good values for work_mem? within the Pgsql Performance forums, part of the PostgreSQL category; --> Bill Moran <wmoran@collaborativefusion.com> writes: > Does the creation of a temp file trigger any logging? No; but it wouldn't ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Bill Moran <wmoran@collaborativefusion.com> writes: > Does the creation of a temp file trigger any logging? No; but it wouldn't be hard to add some if you wanted. I'd do it at deletion, not creation, so you could log the size the file reached. See FileClose() in src/backend/storage/file/fd.c. > That leads to my other question. Assuming I've got lots of > connections (which I do), how can I determine if work_mem is too > high? When you start swapping, you have a problem --- so watch vmstat or local equivalent. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |