On 2013-04-24 19:16:12 +0900, Kyotaro HORIGUCHI wrote: > Hello, > > > > cp: cannot stat `../arc/000000030000000000000013': そのようなファイルやディレクトリはありません > > > [Standby] 2013-04-22 01:27:25 EDTLOG: 00000: restored log file > > > "000000020000000000000013" from archive > > > I can't read the error message here, but this looks suspicious. > > The error message is "No such file or directory" in Japanese :-). > Perhaps restore_command is 'cp ../arc/%f %p'. > > > The recovery command seems to be returning success although it prints such > an error message? > > It seems that, on 9.2.4, RestoreArchivedFile returns expected xlog > filename even if the restore command ends up in failure. And the > caller XLogFileOpen successfully ets and returns fd for the filename > if the file exists since before the restoration attempt. It does not > matter when the existing file and the file expected to be restored are > identical in content.
But thats not what happening here, afaics the "restore log file ..." message is only printed if the returncode is 0. And the return value from RestoreArchivedFile() would be different in the case you describe which would make XLogFileRead() fail, so it should result in different errors. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
