Hi!
Thanks for the answer.
On 01/03/11 18:36, pasman pasmaÅski wrote:
The problem exists when you do a base backup with pg_backup?
Maybe rsync skip some data ?
Yes, problem exists using pg_start/stop_backup as i discribed.
I am sure that 'rsync -avH ...' and 'tar cvf ...' will skip at least
additions made to the filesystem tree after they are started. In this
case rsync says nothing and tar says
tar: directory-name: file changed as we read it
But
http://www.postgresql.org/docs/9.0/interactive/continuous-archiving.html
suggests to use tar on rsync and i guess that PostgreSQL recovery with
wal files takes care of these inconsistencies that are created during
copying filesystem, right?
Imre
------------
pasman
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
