Re: Preventing query from hogging server
| От | Matthew Nuzum |
|---|---|
| Тема | Re: Preventing query from hogging server |
| Дата | |
| Msg-id | 42431f52.4700af57.2963.ffffe2b8@mx.gmail.com обсуждение исходный текст |
| Ответ на | Re: Preventing query from hogging server (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Preventing query from hogging server
|
| Список | pgsql-performance |
> I would strongly suggest doing the min and max calculations together: > > select groupid, min(col), max(col) from ... > > because if you do them in two separate queries 90% of the effort will be > duplicated. > > regards, tom lane Thanks. Other than avoiding using too much sort mem, is there anything else I can do to ensure this query doesn't starve other processes for resources? Doing the explain analyze only increases my server load by 1 and seems to readily relinquish CPU time, but previously when I had been running a test query my server load rose to unacceptable levels. FWIW, the explain was run from psql running on the db server, the test query the other day was run from one of the webservers. Should I run this on the db server to minimize load? -- Matthew Nuzum <matt@followers.net> www.followers.net - Makers of "Elite Content Management System" View samples of Elite CMS in action by visiting http://www.followers.net/portfolio/
В списке pgsql-performance по дате отправления: