I notice in 'pg_data' that a file will stay in pg_xlog until it passes 16 MB,
then it goes to the archive pretty much right away. So, when it's busy you get
a lot of files swapping into the archive , but when it's not you can get one
file taking an hour or more to get up to 16 MB before it swaps over to the
archive. In reading the documentation "every 5 minutes or 36 log file segments
which ever is first" - - 74 files in my case. But I noticed when it's slow
it's more it can be longer than 5 minutes. I'm thinking the "5 minutes or 36
log segments" rule applies to just after files hit 16 MB in size, until then,
they are building up.
Does that all sound right?> To: [EMAIL PROTECTED]> CC:
pgsql-admin@postgresql.org> Subject: Re: [ADMIN] Zen and art if WAL and dump
file mainteance > Date: Mon, 28 Jan 2008 16:27:05 -0500> From: [EMAIL
PROTECTED]> > dx k9 <[EMAIL PROTECTED]> writes:> > We are trying to figure out
why maintenance on A (zipping up & removing files) would have an affect on
production processing (killed it) on pgdata - B.> > Sounds like an OOM kill
problem --- do you have memory overcommit> disabled on that machine?> >
regards, tom lane
_________________________________________________________________
Climb to the top of the charts! Play the word scramble challenge with star
power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan
