pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@surnet.cl>
To: David Parker <dparker@tazznetworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: checkpoint segments
Date: Mon, 16 May 2005 00:39:20 -0400
Message-ID: <20050516043920.GA9292@surnet.cl> (raw)
In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C74609A@corpsrv2.tazznetworks.com>
References: <07FDEE0ED7455A48AC42AC2070EDFF7C74609A@corpsrv2.tazznetworks.com>

On Sun, May 15, 2005 at 08:22:13PM -0400, David Parker wrote:

> In the database log at that time there was a "recycling transaction log"
> message which seems to correspond to the time when the clients were
> paused, though I don't have it concretely correlated. 

Maybe what you need is make the bgwriter more aggressive, so that I/O is
more evenly spread between checkpoint intervals -- that way, at
checkpoint there's less work to do.

> 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)?

Well, recycling is actually a *good* thing -- it saves you from having
to remove WAL segment files and allocate new files for the new logs.  So
what you really want doesn't have anything to do with the recycling
itself, but rather with the simultaneous checkpoint that's going on at
the same time.

-- 
Alvaro Herrera (<alvherre[a]surnet.cl>)
Licensee shall have no right to use the Licensed Software
for productive or commercial use. (Licencia de StarOffice 6.0 beta)



view thread (6+ messages)  latest in thread

Message-ID: <20050516043920.GA9292@surnet.cl>
Permalink:  ../20050516043920.GA9292@surnet.cl/
Also on:    postgresql.org/message-id/20050516043920.GA9292@surnet.cl

 · 

reply

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: alvherre@surnet.cl, dparker@tazznetworks.com
  Subject: Re: checkpoint segments
  In-Reply-To: <20050516043920.GA9292@surnet.cl>

* 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