Re: WAL Optimisation - configuration and usage

Further update to my WAL experimentation. pg_xlog files have increased
to 81, and checking today up to 84. Currently nothing much going on with
the server save a background process running a select every 30 seconds
with almost no impact (according to IO from vmstats).

This in itself is a good sign - an improvement on running last week, but
I'd still like to get clarification on WAL file usage if possible.

Log file tailing has nothing more interesting than a whole set of
"recycled transaction log file" entries :

2004-03-01 16:01:55 DEBUG: recycled transaction log file 0000007100000017
2004-03-01 16:07:01 DEBUG: recycled transaction log file 0000007100000018
2004-03-01 16:17:14 DEBUG: recycled transaction log file 0000007100000019
2004-03-01 16:22:20 DEBUG: recycled transaction log file 000000710000001A
2004-03-01 16:32:31 DEBUG: recycled transaction log file 000000710000001B
2004-03-01 16:37:36 DEBUG: recycled transaction log file 000000710000001C
2004-03-01 16:47:48 DEBUG: recycled transaction log file 000000710000001D
2004-03-01 16:52:54 DEBUG: recycled transaction log file 000000710000001E
2004-03-01 17:03:05 DEBUG: recycled transaction log file 000000710000001F

Looks kinda automated, but the times aren't quite even at around 6-10
minutes apart.

cheers,
--

Rob Fielding
rob(at)dsvr(dot)net

www.dsvr.co.uk Development Designer Servers Ltd