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

From: "Tefft, Michael J" <Michael(dot)J(dot)Tefft(at)snapon(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Cc: "Jain, Ankit" <Ankit(dot)Jain(at)snapon(dot)com>
Subject: "could not write to output file: Permission denied" during pg_dump
Date: 2012-11-10 14:03:01
Message-ID: 8C0087E93F6A9A459051869F5D5748910105D2FD@LISL-XBCK-C1-V2.snaponglobal.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We have several Postgres 9.4 databases on Solaris 10 that are structural
clones but with different data . While running multiple concurrent
pg_dump exports for these databases, we get sporadic errors like this:

pg_dump: dumping contents of table attachment

pg_dump: [custom archiver] could not write to output file: Permission
denied

pg_dump: *** aborted because of error

This is after successfully dumping several tables. The table that
triggers the failure varies from run to run, and is not (or, so far has
not been) the first table processed. These failures only occur during
concurrent runs - we have not seen them when we single-thread the
pg_dump exports.

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}

Any ideas?

Michael Tefft

Snap-on Business Solutions

4025 Kinross Lakes Parkway

Richfield, OH 44286

330-659-1840

Michael(dot)J(dot)Tefft(at)snapon(dot)com

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tefft, Michael J 2012-11-10 14:19:28 Re: "could not write to output file: Permission denied" during pg_dump
Previous Message Greg Williamson 2012-11-10 02:45:45 Re: Unexpectedly high disk space usage RESOLVED (Manual reindex/vacuum)