Re: sort_mem param of postgresql.conf
От | Scott Marlowe |
---|---|
Тема | Re: sort_mem param of postgresql.conf |
Дата | |
Msg-id | dcc563d10811131017l29e65601vabdd1699f3e4ee44@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: sort_mem param of postgresql.conf ("Scott Marlowe" <scott.marlowe@gmail.com>) |
Список | pgsql-general |
2008/11/13 Scott Marlowe <scott.marlowe@gmail.com>: > On Thu, Nov 13, 2008 at 7:59 AM, Grzegorz Jaśkiewicz <gryzman@gmail.com> wrote: >> >> >> On Wed, Nov 12, 2008 at 11:08 PM, Greg Smith <gsmith@gregsmith.com> wrote: >>> >>> Be advised that the work_mem setting (and its deprecated alias sort_mem) >>> are on a per-client basis. So if you have a bunch of people running reports >>> with that setting, you might discover your server running out of memory; >>> that's a really high setting. Generally, if it's only a report or two that >>> need a lot more working memory for sorts, you can do this at the beginning >>> of them instead: >>> >>> set work_mem='512MB'; >> >> so how do I change it back to default (without knowing what the previous val >> was). I suppose having it in a transaction won't do :P > > default is 1M, but you can safely run 8 to 16 Meg with your setup. Wait I might be confusing you with someone else. What's your machine's mem, how much is shared_buffers, and what's your max_connections?
В списке pgsql-general по дате отправления: