From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: "David Parker" <dparker@tazznetworks.com>
Subject: Re: checkpoint segments
Date: Sun, 15 May 2005 20:26:02 -0700
User-Agent: KMail/1.8
Cc: pgsql-performance@postgresql.org
References: <07FDEE0ED7455A48AC42AC2070EDFF7C74609A@corpsrv2.tazznetworks.com>
In-Reply-To: 
 <07FDEE0ED7455A48AC42AC2070EDFF7C74609A@corpsrv2.tazznetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200505152026.02262.josh@agliodbs.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