Thread: BUG #6479: Wrong Slash in pg_restore
The following bug has been logged on the website: Bug reference: 6479 Logged by: Mike Keller Email address: mikekeller987@frontier.com PostgreSQL version: 9.1.2 Operating system: Windows 7 x64 Description:=20=20=20=20=20=20=20=20 I haven't been able to get pg_restore to restore a backup from pg_dump. When doing a restore from a Directory backup I noticed that pg_restore is using a forward slash instead of the required back slash when searching for toc.dat. I suspect that it is also doing the same thing for custom and tar backups as well. The lack of ability to Automate backups is preventing me from proposing PostgreSQL for Windows as a Database solution I have been assigned to work on.
On 02/21/12 6:22 AM, mikekeller987@frontier.com wrote: > I haven't been able to get pg_restore to restore a backup from pg_dump. > When doing a restore from a Directory backup I noticed that pg_restore is > using a forward slash instead of the required back slash when searching for > toc.dat. I suspect that it is also doing the same thing for custom and tar > backups as well. windows filesystem APIs are perfectly happy with forward slashes in paths, always have been. -- john r pierce N 37, W 122 santa cruz ca mid-left coast
John R Pierce <pierce@hogranch.com> writes: > On 02/21/12 6:22 AM, mikekeller987@frontier.com wrote: >> I haven't been able to get pg_restore to restore a backup from pg_dump. >> When doing a restore from a Directory backup I noticed that pg_restore is >> using a forward slash instead of the required back slash when searching for >> toc.dat. I suspect that it is also doing the same thing for custom and tar >> backups as well. > windows filesystem APIs are perfectly happy with forward slashes in > paths, always have been. ISTM we've heard of Windows antivirus add-ons that break this, which of course is just one of many varieties of fail in that industry. But yeah, the stated complaint is not by itself a bug, and it would help a lot if the OP had shown us what he's doing and what happens instead of jumping to conclusions about why it's not working for him. regards, tom lane