Imre Oolberg <imre@xxxxxxxxxxx> writes: > First of all, thanks for your time dealing with my situation. I must > stress that i have wal arhived starting from before issuing > pg_start_backup, wal archives generated before pg_start/stop_backup and > also some wal archive files generated after pg_stop_backup (and > permissions are ok). But for some reason my replay starts exactly where > .backup file says 'stop wal location', referring to my earlier post > STOP WAL LOCATION: 1/6325B2E0 (file 000000010000000100000063) > I am starting to think more in the direction what Kevin Grittner > suggested that i miss something in my procedure and instead following so > to say recovery path i am doing something else which strangely ends up > with working database process but actually misses some data. I wonder whether you're failing to copy the backup_label file as part of the base backup. The presence of that file is what tells the slave postmaster where it has to start recovering from. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
