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

From: "Abraham Grief" <abraham(dot)grief(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4726: pg_dumpall -f doesn't report error when file can't be opened
Date: 2009-03-23 12:45:11
Message-ID: 200903231245.n2NCjB25061554@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 4726
Logged by: Abraham Grief
Email address: abraham(dot)grief(at)gmail(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-03-23 14:19:52 Re: BUG #4726: pg_dumpall -f doesn't report error when file can't be opened
Previous Message Tom Lane 2009-03-23 02:05:43 Re: BUG #4725: conflict with f-secure