Re: Postgres query completion status?
| От | Richard Neill |
|---|---|
| Тема | Re: Postgres query completion status? |
| Дата | |
| Msg-id | 4B07062F.1070803@cam.ac.uk обсуждение исходный текст |
| Ответ на | Re: Postgres query completion status? ("Fernando Hevia" <fhevia@ip-tel.com.ar>) |
| Ответы |
Re: Postgres query completion status?
Re: Postgres query completion status? |
| Список | pgsql-performance |
Fernando Hevia wrote: > > >> -----Mensaje original----- >> De: Richard Neill >> >> >> max_connections = 500 # (change requires restart) >> work_mem = 256MB # min 64kB > > Not that it has to do with your current problem but this combination could > bog your server if enough clients run sorted queries simultaneously. > You probably should back on work_mem at least an order of magnitude. > What's the correct way to configure this? * We have one client which needs to run really big transactions (therefore needs the work memory). * We also have about 200 clients which run always very small, short queries. Richard
В списке pgsql-performance по дате отправления: