Re: "could not write to output file: Permission denied" during pg_dump

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: "Tefft, Michael J" <Michael(dot)J(dot)Tefft(at)snapon(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: "could not write to output file: Permission denied" during pg_dump
Date: 2012-11-10 15:11:33
Message-ID: 509E6EA5.4080608@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/10/2012 06:19 AM, Tefft, Michael J wrote:
> Correction, that should have been Postgres 9.0.4 not 9.4.
>

For some reason I did not get the original question. Found it in the
archives.

In that post you show the following:

The command used to invoke pg_dump is as follows:

${currentCodeDir}/thirdPartyLinks/postgres/bin/pg_dump
--file=${currentDataDir}/${db_name}.dmp --format=custom
--host=${PostgreSQLServer} --port=${db_port} --username=xxxx
--no-privileges --verbose ${db_name}

You say you are doing concurrent dumps of multiple databases.

Are talking different databases in different clusters or different
databases in a cluster?

If different databases in different clusters do they have the same name
in each cluster?

If so have you checked that: '--file=${currentDataDir}/${db_name}.dmp'
is not writing to the same file?

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-11-10 15:27:16 Re: "could not write to output file: Permission denied" during pg_dump
Previous Message Tefft, Michael J 2012-11-10 14:19:28 Re: "could not write to output file: Permission denied" during pg_dump