Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Re: Full statement logging problematic on larger machines? - Mailing list pgsql-performance

From Laurent Laborde
Subject Re: Full statement logging problematic on larger machines?
Date
Msg-id 8a1bfe660903121432k153f7c8u3f86c1ae4b7f1551@mail.gmail.com
Whole thread Raw
In response to Re: Full statement logging problematic on larger machines?  (Frank Joerdens <frank@joerdens.de>)
Responses Re: Full statement logging problematic on larger machines?
Re: Full statement logging problematic on larger machines?
List 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 by date:

Previous
From: Greg Smith
Date:
Subject: Re: Proposal of tunable fix for scalability of 8.4
Next
From: Scott Carey
Date:
Subject: Re: Proposal of tunable fix for scalability of 8.4