If pg_start_backup is used correctly, no data pages will be written to disk until pg_stop_backup is called, so this shouldn't be an issue - HOWEVER - check that you're excluding your pg_xlog directory (within your database directory) from the tar backup as these will be changing.
Whatever archive utility you're using, if a file is being changed at the time of reading, it won't be archived correctly. Andy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rajesh Kumar Mallah Sent: Tuesday, 28 March, 2006 5:27 PM To: Tom Lane Cc: [EMAIL PROTECTED]; pgsql-admin@postgresql.org Subject: Re: FW: [ADMIN] Setting up of PITR system. --- secondly , i was asking about the tool for copying the database directory not the one for archiving the logs. when i use tar , it gives warning that the file changed while it was reading the file, i need a tool that does not give warning for this kind of activity. --- ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
