pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tory M Blue <tmblue@gmail.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres 8.2 memory weirdness
Date: Sun, 27 Jan 2008 22:09:12 -0800
Message-ID: <8a547c840801272209n4b6cfa0ch1ecdc5018b940c9f@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0801251256540.4724@westnet.com>
References: <8a547c840801231023q55796128nb2e88b8c8cfe86e@mail.gmail.com>
	<Pine.GSO.4.64.0801231923420.12679@westnet.com>
	<8a547c840801240946n37c7fad6ycf62187f82b2027c@mail.gmail.com>
	<Pine.GSO.4.64.0801241335180.7217@westnet.com>
	<8a547c840801250936w59aad548w268f24a5fcc89ccf@mail.gmail.com>
	<Pine.GSO.4.64.0801251256540.4724@westnet.com>

On Jan 27, 2008 4:08 PM, Greg Smith <gsmith@gregsmith.com> wrote:

>
> More segments means more disk space taken up with them and a longer crash
> recovery.  Those are the downsides; if you can live with those there's no
> reason to run at <100 if that works for you.  Fine-tuning here isn't
> really that helpful.
>
> I'm a little confused by your report through because you should still be
> seeing regular checkpoint warnings if you set checkpoint_warning = 3600s ,
> they should just be spaced further apart.

I'm not seeing any warnings at all.

[idb01 ~]$ sudo cat /data/logs/pgsql-27.log  | grep -i check
[idb01 ~]$ sudo cat /data/logs/pgsql-26.log  | grep -i check
[idb01 ~]$ sudo cat /data/logs/pgsql-25.log  | grep -i check
[idb01 ~]$ sudo cat /data/logs/pgsql-24.log  | grep -i check
2008-01-24 03:54:39 PST    LOG:  checkpoints are occurring too
frequently (89 seconds apart)
2008-01-24 03:54:39 PST    HINT:  Consider increasing the
configuration parameter "checkpoint_segments".
2008-01-24 07:26:25 PST    LOG:  checkpoints are occurring too
frequently (106 seconds apart)
2008-01-24 07:26:25 PST    HINT:  Consider increasing the
configuration parameter "checkpoint_segments".
2008-01-24 11:34:18 PST    LOG:  checkpoints are occurring too
frequently (173 seconds apart)
2008-01-24 11:34:18 PST    HINT:  Consider increasing the
configuration parameter "checkpoint_segments".

Segment config still:

# - Checkpoints -
checkpoint_segments = 100               # bumped from 50
checkpoint_timeout = 300                # range 30s-1h
#checkpoint_warning = 30s               # 0 is off
checkpoint_warning = 3600s              # 0 is off

No warnings in my logs, I see some LOG information but it pertains to
slon and not postgres directly.

Ideas?!

Thanks again

Tory



view thread (7+ messages)

Message-ID: <8a547c840801272209n4b6cfa0ch1ecdc5018b940c9f@mail.gmail.com>
Permalink:  ../8a547c840801272209n4b6cfa0ch1ecdc5018b940c9f@mail.gmail.com/
Also on:    postgresql.org/message-id/8a547c840801272209n4b6cfa0ch1ecdc5018b940c9f@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: tmblue@gmail.com, gsmith@gregsmith.com
  Subject: Re: Postgres 8.2 memory weirdness
  In-Reply-To: <8a547c840801272209n4b6cfa0ch1ecdc5018b940c9f@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