daveg wrote: > > I'd like to propose adding a new GUC to limit the amount of memory a backend > can allocate for its own use. The problem this addresses is that sometimes > one needs to set work_mem fairly high to get good query plans for large joins. > However, some complex queries will then use huge amounts of memory so that > one or a few of them will consume all the memory on the host and run it deep > into swap or trigger the oom killer or worse.
Oh, BTW, did anyone get interested in adding the bits to disable the OOM killer for postmaster on the various Linux initscripts? It needs some games with /proc/<pid>/oom_adj and requires root privileges, but I think an initscript is in an excellent position to do it. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
