From: Kevin Kempter <kevin@kevinkempterllc.com>
To: pgsql-admin@postgresql.org
Subject: Re: Understanding wal segments
Date: Thu, 1 Nov 2007 22:39:07 -0600
Message-ID: <200711012239.07980.kevin@kevinkempterllc.com> (raw)
In-Reply-To: <21716.1193978282@sss.pgh.pa.us>
References: <200711012155.16409.kevin@kevinkempterllc.com>
<21716.1193978282@sss.pgh.pa.us>
On Thursday 01 November 2007 22:38:02 Tom Lane wrote:
> Kevin Kempter <kevin@kevinkempterllc.com> writes:
> > What's the relationship between wal_buffers and checkpoint_segments?
>
> None particularly.
>
> > even
> > though the max distance between checkpoints is 32 segments, is there
> > something that controls the number of files/segments in the pg_xlog dir ?
>
> The system is designed to settle at 2*checkpoint_segments+1 files in
> pg_xlog, assuming that you have activity spikes sufficient to drive it
> up to that level at all.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
makes sense. our system cetrtianly has the activity needed to push it to that
level. I turned on wal archivint 1hr & 10min ago and I already have 135 wal
segments in my archive directory. I'm running a file system backup, I did a
pg_start_backup and now I'm running the tar. Will this affect the transaction
activity? I thought it would not.
Also I suspect after each filesystem backup I should remove the older archived
segments since the file system backup makes them irrelevant. Is this
accurate?
Thx
/Kevin
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-admin@postgresql.org
Cc: kevin@kevinkempterllc.com
Subject: Re: Understanding wal segments
In-Reply-To: <200711012239.07980.kevin@kevinkempterllc.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