From: | Brendan Duddridge <brendan(at)clickspace(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Postgresql-General General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: WAL Archiving frequency |
Date: | 2006-04-01 06:39:46 |
Message-ID: | FC1BE4DC-809A-40C6-A537-872DD3B8F0DA@clickspace.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks Tom,
I just didn't know if that was normal or not. I actually saw 4 WAL
files / minute today. I set checkpoint_segments = 128, so maybe that
will help.
Thanks,
____________________________________________________________________
Brendan Duddridge | CTO | 403-277-5591 x24 | brendan(at)clickspace(dot)com
ClickSpace Interactive Inc.
Suite L100, 239 - 10th Ave. SE
Calgary, AB T2G 0V9
On Mar 31, 2006, at 8:47 PM, Tom Lane wrote:
> Brendan Duddridge <brendan(at)clickspace(dot)com> writes:
>> I've noticed that it's archiving the 16 MB wal files about once every
>> minute. Is this normal? There's a huge number of files in my
>> wal_archives directory now.
>> Is there a parameter to tell it not to archive so frequently? Or is
>> this nothing to be too concerned about?
>
> If you've got a reasonably active database, 16MB/minute is not an
> unlikely rate of WAL generation. You can probably slow it down a
> bit by
> increasing the checkpoint-spacing parameters, but you can't just say
> "don't generate so much WAL please". Either you want a log or you
> don't.
>
> Basically, you have to take base backups often enough that the total
> number of WAL archive files needed stays under your threshold of
> pain...
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas F. O'Connell | 2006-04-01 07:07:09 | pgpool ABORT + no transaction warning |
Previous Message | shakahshakah@gmail.com | 2006-04-01 06:08:48 | 8.1.3, libpq, PQprepare, plpgsql function, and partitioned tables |