Re: Full statement logging problematic on larger machines?

From: Laurent Laborde <kerdezixe(at)gmail(dot)com>
To: Frank Joerdens <frank(at)joerdens(dot)de>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Full statement logging problematic on larger machines?
Date: 2009-03-12 21:32:59
Message-ID: 8a1bfe660903121432k153f7c8u3f86c1ae4b7f1551@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, Mar 11, 2009 at 11:42 PM, Frank Joerdens <frank(at)joerdens(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Carey 2009-03-12 21:45:54 Re: Proposal of tunable fix for scalability of 8.4
Previous Message Greg Smith 2009-03-12 20:35:31 Re: Proposal of tunable fix for scalability of 8.4