Magnus Hagander <mag...@hagander.net> wrote: > Comments and contributions are most welcome. This is probably too esoteric to be worked on yet, but for this to be useful for us we would need to pass the resulting files through pg_clearxlogtail and gzip in an automated fashion. And we would need to do regular log file archiving in parallel with it. As background, our databases around the state archive to a directory which is then pushed via rsync to a "dumb" backup location in the same room as the database server (we're lucky to have rsync on the target of this copy; any other executable is out of the question), and the same directory is pulled via rsync to a central location. We would be interested in using streaming replication to a tool such as you describe for the copy to the central location, but since we would still be forcing a wal-file switch once per hour we would need the current capability to shrink an "empty" file from 16MB to 16kB using the above-mentioned tools. Also, a the ability to limit bandwidth would be a nice feature for us, preferably in a way which could be changed on the fly. If you could keep the development "friendly" to such features, I may get around to adding them to support our needs.... -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers