| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Abraham Grief" <abraham(dot)grief(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4726: pg_dumpall -f doesn't report error when file can't be opened |
| Date: | 2009-03-23 14:19:52 |
| Message-ID: | 8550.1237817992@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Abraham Grief" <abraham(dot)grief(at)gmail(dot)com> writes:
> I ran pg_dumpall on Windows Vista with the -f option. However, I wasn't
> running the command as an administrator, and I specified a path that I
> wasn't allowed to write to. The dump completed with no errors, and no file
> was created.
> Instead, I should have received an error message as soon as I ran the
> command that informed me that the file I specified could not be opened for
> writing.
Works for me ...
$ pg_dumpall -f /no/such/file
pg_dumpall: could not open the output file "/no/such/file": No such file or directory
$ pg_dumpall -f /usr/dumpfile
pg_dumpall: could not open the output file "/usr/dumpfile": Permission denied
Maybe you need to use a real operating system. The pg_dumpall code is
definitely testing for open failures, so the only way this doesn't
work is if there's a system-level problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lorenzo | 2009-03-24 15:30:06 | BUG #4727: Unable to drop table for cache lookup failed for relation |
| Previous Message | Abraham Grief | 2009-03-23 12:45:11 | BUG #4726: pg_dumpall -f doesn't report error when file can't be opened |