pg_dump on windows (I know) causes "could not stat file" error on 2 files

Highlighted
Adventurer

pg_dump on windows (I know) causes "could not stat file" error on 2 files

Hi there,

we try to create a directory running version 11.3. on windows 2012 r2.

The pg_dump output lists an error for 2 files:

pg_dump: could not stat file "(file_path)": Unknown error

The files are 5.8 GB and 2.2 GB in size.

We reproduced the behaviour on 11.4 and 10.9.

A pg_restore however works fine and lists no error.

 

Has anybody an explanation, ideas on this?

 

Best regards,

Michael

Archived Discussions


Effective March 31st, we will no longer engage on PostgresRocks.


How to engage with us further?


  • Thought Leadership: EDB Blogs

  • Tips and Tricks: Postgres Tutorials

  • Customer Support: Create a Case Please note: Only customers with an active EDB support subscription and support portal authorization can create support ticket

  • Engage on Stackoverflow While engaging on Stackoverflow tag the question with EDB or EnterpriseDB.

3 REPLIES 3
Highlighted
EDB Team Member

Re: pg_dump on windows (I know) causes "could not stat file" error on 2 files

Hi Michael,

It looks like it is a bug, you can refer the below mail thread.

https://www.postgresql.org/message-id/153442391458.1505.9181095584291689853%40wrigleys.postgresql.or...

Could you please confirm the Postgresql binary version, which you are using to take a dump.

Highlighted
Adventurer

Re: pg_dump on windows (I know) causes "could not stat file" error on 2 files

Hi sachinfate,

thanks for the quick reply.

The original error occured on windows 2012 r2 using postgresql version

"PostgreSQL 11.3, compiled by Visual C++ build 1914, 64-bit"

Then I reran the pg_dump on my notebook (Windows 10 Pro 1803) twice.

Once on PostgreSQL 11.3, then on PostgreSQL 10.9.

 

sachinfate
Highlighted
Adventurer

Re: pg_dump on windows (I know) causes "could not stat file" error on 2 files

...I always used the pg_dump binary that comes with the postgresql server on the server itself.

© 2019 EnterpriseDB Corporation. All rights reserved.   |   Privacy Policy   |  Terms of Use   |   Trademarks