The dump is over 3GB. So there's no question this is it. I had a
feeling this would all come down to not being on the latest version.
Thanks to both Tom and Magnus for your help.
Tom Lane wrote:
William Garrison <[EMAIL PROTECTED]> writes:
I'm embarrassed to say it is 8.2.3 :( I'm not s
William Garrison <[EMAIL PROTECTED]> writes:
> I'm embarrassed to say it is 8.2.3 :( I'm not sure why they haven't
> upgraded our production servers to the latest 8.2 yet. It's running on
> Windows Server 2003, and it looks like there is plenty of disk space.
Hmm. There was an 8.2.4 bug fix
yay!
Thank you.
Magnus Hagander wrote:
This is almost certainly the bug fixed in 8.2.4 and listed in the
release notes as:
"Allow pg_dump to do binary backups larger than two gigabytes on Windows
(Magnus) "
If it happens to be that your dump could approach the 2Gb limit, I
sugge
This is almost certainly the bug fixed in 8.2.4 and listed in the
release notes as:
"Allow pg_dump to do binary backups larger than two gigabytes on Windows
(Magnus) "
If it happens to be that your dump could approach the 2Gb limit, I
suggest you upgrade to 8.2.9 and see if it goes away.
As this
I'm embarrassed to say it is 8.2.3 :( I'm not sure why they haven't
upgraded our production servers to the latest 8.2 yet. It's running on
Windows Server 2003, and it looks like there is plenty of disk space.
I googled this and found someone reported defect 2461 for this, some
time ago, but
William Garrison <[EMAIL PROTECTED]> writes:
> Our IT administrator ran a pg_dump and received the following error:
> pg_dump: [custom archiver] WARNING: ftell mismatch with expected
> position -- ftell used
What platform, and exactly what version of pg_dump? Is it possible
you ran out of disk s
Our IT administrator ran a pg_dump and received the following error:
.
.
.
pg_dump: dumping contents of table history
pg_dump: [custom archiver] WARNING: ftell mismatch with expected
position -- ftell used
pg_dump: dumping contents of table history_archive
pg_dump: [custom archiver] WARNING: fte
