Re: Full statement logging problematic on larger machines?

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: Frank Joerdens <frank(at)joerdens(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Nic Ferrier <nic(at)woome(dot)com>, Avleen Vig <avleen(at)woome(dot)com>, Mike Rogers <mike(dot)rogers(at)woome(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Full statement logging problematic on larger machines?
Date: 2009-03-12 13:45:32
Message-ID: 200903121445.35481.dfontaine@hi-media.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thursday 12 March 2009 14:38:56 Frank Joerdens wrote:
> I just put the patched .deb on staging and we'll give it a whirl there
> for basic sanity checking - we currently have no way to even
> approximate the load that we have on live for testing.

Is it a capacity problem or a tool suite problem?
If the latter, you could try out tsung:
http://archives.postgresql.org/pgsql-admin/2008-12/msg00032.php
http://tsung.erlang-projects.org/

Regards,
--
dim

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2009-03-12 14:07:39 Re: Proposal of tunable fix for scalability of 8.4
Previous Message Frank Joerdens 2009-03-12 13:38:56 Re: Full statement logging problematic on larger machines?