Re: Full statement logging problematic on larger machines?

Поиск
Список
Период
Сортировка
От Laurent Laborde
Тема Re: Full statement logging problematic on larger machines?
Дата
Msg-id 8a1bfe660903121432k153f7c8u3f86c1ae4b7f1551@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Full statement logging problematic on larger machines?  (Frank Joerdens <frank@joerdens.de>)
Ответы Re: Full statement logging problematic on larger machines?  (sathiya psql <sathiya.psql@gmail.com>)
Re: Full statement logging problematic on larger machines?  (Frank Joerdens <frank@joerdens.de>)
Список pgsql-performance
On Wed, Mar 11, 2009 at 11:42 PM, Frank Joerdens <frank@joerdens.de> wrote:
>
> effective_cache_size            = 4GB

Only 4GB with 64GB of ram ?

About logging, we have 3 partition :
- data
- index
- everything else, including logging.

Usually, we log on a remote syslog (a dedicated log server for the
whole server farm).

For profiling (pgfouine), we have a crontab that change the postgresql
logging configuration for just a few mn.
and log "all" on the "everything but postgresql" partition.

around 2000 query/seconds/servers, no problem.


--
Laurent Laborde
Sysadmin at JFG-Networks / Over-blog

В списке pgsql-performance по дате отправления:

Предыдущее
От: Greg Smith
Дата:
Сообщение: Re: Proposal of tunable fix for scalability of 8.4
Следующее
От: Scott Carey
Дата:
Сообщение: Re: Proposal of tunable fix for scalability of 8.4