Re: recovery_target_time ignored or recovery alwaysrecovers to end of WAL
От | Jason L. Buberel |
---|---|
Тема | Re: recovery_target_time ignored or recovery alwaysrecovers to end of WAL |
Дата | |
Msg-id | 468925F7.3070304@buberel.org обсуждение исходный текст |
Ответ на | Re: recovery_target_time ignored or recovery alwaysrecovers to end of WAL (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: recovery_target_time ignored or recovery always recovers
to end of WAL
Re: recovery_target_time ignored or recoveryalwaysrecovers to end of WAL |
Список | pgsql-general |
Harrumph - I downloaded the latest xlogdump source, and built/installed it against my 8.2.4 source tree. When I execute it however, I am informed that all of my WAL files (either the 'active' copies in pg_xlog or the 'archived' copies in my /pgdata/archive_logs dir) appear to be malformed: $ /opt/postgres-8.2.4/bin/xlogdump --port 54824 --host 127.0.0.1 --user postgres ../../../archive_logs/* ../../../archive_logs/000000010000000F0000007C: Bogus page magic number D05E at offset 0 invalid record length at F/7C00001C ../../../archive_logs/000000010000000F0000007C.00550700.backup: Partial page of 241 bytes ignored ../../../archive_logs/000000010000000F0000007D: Bogus page magic number D05E at offset 0 invalid record length at F/7D00001C ../../../archive_logs/000000010000000F0000007D.0006C01C.backup: Partial page of 241 bytes ignored Which does not help particularly much :) I'll keep plugging away at this - perhaps my problem in setting the database state to a PITR is related to timezones or timestamp formatting? -jason Tom Lane wrote: > Jason, if you can't figure it out you might grab xlogviewer > http://pgfoundry.org/projects/xlogviewer/ > and see what it says the timestamps of the commit records in your WAL > files are. >
В списке pgsql-general по дате отправления: