Sounds like a file sharing issue. In other words..writing to the same
file at the same time...from two separate pg_dump streams.
Perhaps adding a time var to the file name call below
and see if the error goes away.
On Sat, 2012-11-10 at 08:03 -0600, Tefft, Michael J wrote:
> 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.j.te...@snapon.com
>
>
>
>
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
