From: Josh Berkus <josh@agliodbs.com>
To: David Parker <dparker@tazznetworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: checkpoint segments
Date: Sun, 15 May 2005 20:26:02 -0700
Message-ID: <200505152026.02262.josh@agliodbs.com> (raw)
In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C74609A@corpsrv2.tazznetworks.com>
References: <07FDEE0ED7455A48AC42AC2070EDFF7C74609A@corpsrv2.tazznetworks.com>
David,
> I've seen these messages in the log before, and am aware of the need to
> increase checkpoint_segments, but I wasn't aware that recycling a
> transaction log could be that damaging to performance. There may have
> been some local hiccup in this case, but I'm wondering if recycling is
> known to be a big hit in general, and if I should strive to tune so that
> it never happens (if that's possible)?
Yes, and yes. Simply allocating more checkpoint segments (which can eat a
lot of disk space -- requirements are 16mb*(2 * segments +1) ) will prevent
this problem.
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, dparker@tazznetworks.com
Subject: Re: checkpoint segments
In-Reply-To: <200505152026.02262.josh@agliodbs.com>
* 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