Re: BUG #15333: pg_dump error on large table -- "pg_dump: could not stat file...Unknown error"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Lai <mark(dot)lai(at)integrafec(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15333: pg_dump error on large table -- "pg_dump: could not stat file...Unknown error"
Date: 2018-08-17 14:53:11
Message-ID: 5632.1534517591@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Mark Lai <mark(dot)lai(at)integrafec(dot)com> writes:
> I ran the dump on the large table with no jobs flag and got the same error.
> ...
> The dump was successful on a small table.

Weird indeed. Can any Windows developers reproduce this and poke into it?

I have a sneaking suspicion that this is related to Windows' known issues
with concurrently-opened files, but it's pretty hard to see why there
would be a dependency on the size of the file.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nandakumar M 2018-08-17 15:40:34 Row exists in a table that violates Foreign key constraint
Previous Message Andrew Gierth 2018-08-17 14:38:41 Re: BUG #15336: Wrong cursor's bacward fetch results in select with ALL(subquery)