| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | c_michal(at)poczta(dot)onet(dot)pl |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15942: not working function pg_stat_file |
| Date: | 2019-08-07 21:44:30 |
| Message-ID: | 22988.1565214270@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> I create 2 GB file:
> ...
> (and then pg_stat_file fails on it)
Yeah, this is a known problem on Windows: it provides a stat() function
that fails on large files. There's been some discussion of how we might
work around that, most recently here:
https://www.postgresql.org/message-id/flat/1803D792815FC24D871C00D17AE95905CF5099%40g01jpexmbkw24
but that hasn't been turned into a patch and you shouldn't
hold your breath waiting for it to happen :-(. There's probably
no chance that the eventual fix would be safe to back-patch into
existing release branches, either.
So ... we might have a fix for this someday, but probably not soon.
It is annoying that we're just reporting "Unknown error" though.
That could be improved to show something more specific without
a lot of work, I imagine.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-08-08 04:44:43 | BUG #15943: Valgrind-detected error in SlruPhysicalWritePage |
| Previous Message | PG Bug reporting form | 2019-08-07 20:07:27 | BUG #15942: not working function pg_stat_file |