Re: Postgres 8.2 memory weirdness - Mailing list pgsql-performance

From Tory M Blue
Subject Re: Postgres 8.2 memory weirdness
Date
Msg-id 8a547c840801272209n4b6cfa0ch1ecdc5018b940c9f@mail.gmail.com
Whole thread Raw
In response to Re: Postgres 8.2 memory weirdness  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: "Stephen Denne"
Date:
Subject: Re: 8.3rc1 Out of memory when performing update
Next
From: "Guillaume Smet"
Date:
Subject: Re: 8.3rc1 Out of memory when performing update