Steve <cheetah@xxxxxxxxxx> writes: > - What is temp_buffers used for exactly? Temporary tables. Pages of temp tables belonging to your own backend don't ever get loaded into the main shared-buffers arena, they are read into backend-local memory. temp_buffers is the max amount (per backend) of local memory to use for this purpose. > - Do full_page_writes and wal_buffers settings matter AT ALL for a machine > where fysnc = off ? Yes. > - What does wal_buffers mean and does increasing this value actually help > anything? It's the amount of space available to buffer WAL log data that's not been written to disk. If you have a lot of short transactions then there's not much benefit to increasing it (because the WAL will be getting forced to disk frequently anyway) but I've heard reports that for workloads involving long single transactions bumping it up to 64 or 100 or so helps. > - Any idea if this is a smart configuration for this machine? Um ... you didn't mention which PG version? > # This value is going to probably set off cries of using this as a set > # command instead of a big global value; No kidding. You do NOT want work_mem that high, at least not without an extremely predictable, simple workload. > wal_buffers = 512MB I haven't heard any reports that there's a point in values even as high as 1 meg for this. regards, tom lane
