pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Petrilli <petrilli@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Impact of checkpoint_segments under continual load conditions
Date: Sun, 17 Jul 2005 13:08:34 -0400
Message-ID: <59d991c4050717100874c08a86@mail.gmail.com> (raw)

I have a unique scenerio.  My DB is under "continual load", meaning
that I am constantly using COPY to insert new data into the DB.  There
is no "quiet period" for the database, at least not for hours on end. 
Normally, checkpoint_segments can help absorb some of that, but my
experience is that if I crank the number up, it simply delays the
impact, and when it occurs, it takes a VERY long time (minutes) to
clear.

Thoughts?
Chris
-- 
| Christopher Petrilli
| petrilli@gmail.com



view thread (28+ messages)  latest in thread

Message-ID: <59d991c4050717100874c08a86@mail.gmail.com>
Permalink:  ../59d991c4050717100874c08a86@mail.gmail.com/
Also on:    postgresql.org/message-id/59d991c4050717100874c08a86@mail.gmail.com

 · 

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: petrilli@gmail.com
  Subject: Re: Impact of checkpoint_segments under continual load conditions
  In-Reply-To: <59d991c4050717100874c08a86@mail.gmail.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