From: Tom Lane <tgl@sss.pgh.pa.us>
To: Frank Joerdens <frank@joerdens.de>
Cc: pgsql-performance@postgresql.org, Nic Ferrier <nic@woome.com>
Cc: Avleen Vig <avleen@woome.com>
Cc: Mike Rogers <mike.rogers@woome.com>
Subject: Re: Full statement logging problematic on larger machines?
Date: Wed, 11 Mar 2009 16:46:10 -0400
Message-ID: <3401.1236804370@sss.pgh.pa.us> (raw)
In-Reply-To: <7d10d2df0903111227g2e40e742g5992cba5158dd4d2@mail.gmail.com>
References: <7d10d2df0903111227g2e40e742g5992cba5158dd4d2@mail.gmail.com>
Frank Joerdens <frank@joerdens.de> writes:
> Greetings. We're having trouble with full logging since we moved from
> an 8-core server with 16 GB memory to a machine with double that
> spec and I am wondering if this *should* be working or if there is a
> point on larger machines where logging and scheduling seeks of
> background writes - or something along those lines; it might be a
> theory - doesn't work together any more?
You didn't tell us anything interesting about *how* you are logging,
so it's hard to comment on this. Are you just writing to stderr?
syslog? using PG's built-in log capture process? It would be good
to show all of your log-related postgresql.conf settings.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, frank@joerdens.de, nic@woome.com, avleen@woome.com, mike.rogers@woome.com
Subject: Re: Full statement logging problematic on larger machines?
In-Reply-To: <3401.1236804370@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox