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. > and the key-based login was broken for a few weeks (I just noticed). I suggest you get some monitoring in place to prevent this from being a problem in the future. > 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. Sorry. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
