On Thu, Jan 7, 2010 at 11:29 AM, Alvaro Herrera <alvherre@xxxxxxxxxxxxxxxxx> wrote: > Aleksey Tsalolikhin escribió: > >> I do have a cron job that cleans files older than 2 days out of the >> pg_xlog directory; > > Bad, bad idea. Get rid of that. Perfect way to corrupt your system. > Postgres removes pg_xlog files automatically when they are no longer > necessary. If it doesn't remove them, something is happening and you > need to fix *that*. Deleting files by hand only works around the > wasted-disk-space symptom in a bad way. Completely agreed. >> How do I get Postgres to stop trying to rsync >> 00000001000000350000006E, and to do rsync all the WAL files that ARE >> there? > > You're screwed. You need to get a new base backup; all the files > you have archived previous to 00000001000000350000006E are useless. > > You can get out of the problem by creating a dummy file with that name > in pg_xlog, but keep in mind that the archive is now completely useless > and unrecoverable. Or remove pg_xlog/archive_status/00000001000000350000006E.ready instead of creating a dummy file. Postgres tries to archive the WAL files whose .ready file exists in archive_status directory. And, note that you must get out of the archiving problem *before* making a new base backup because pg_stop_backup() waits until the last WAL file filled during backup has been archived. Otherwise, pg_stop_backup() would get stuck. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
