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

Kevin Kempter <kevin@kevinkempterllc.com> writes: > 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? Depends what your goals are. If you only want to be able to recover the latest database state then you only need archived WAL segments back to the start of the latest filesystem backup. If you are interested in the "PITR" aspect of it --- being able to revert back to last Tuesday before some bad guy injected bad data, say --- then you'll want to keep older filesystem backups too, and a continuous string of archived WAL files covering the period of interest. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster

Kevin Kempter <kevin@kevinkempterllc.com> writes: > One more question. I see a fair amount of file changed warnings in the tar > output. Like this: > tar: ./data/base/82097725/4242350944: file changed as we read it Yeah, GNU tar complains about that. It's not a problem, other than the risk that a boatload of such warnings could obscure real problems ... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match