BUG #4726: pg_dumpall -f doesn't report error when file can't be opened - Mailing list pgsql-bugs

From Abraham Grief
Subject BUG #4726: pg_dumpall -f doesn't report error when file can't be opened
Date
Msg-id 200903231245.n2NCjB25061554@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #4726: pg_dumpall -f doesn't report error when file can't be opened  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      4726
Logged by:          Abraham Grief
Email address:      abraham.grief@gmail.com
PostgreSQL version: 8.3.7
Operating system:   Windows Vista
Description:        pg_dumpall -f doesn't report error when file can't be
opened
Details:

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.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4724: Array index out of bounds
Next
From: Tom Lane
Date:
Subject: Re: BUG #4726: pg_dumpall -f doesn't report error when file can't be opened