From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | jub4(at)email(dot)cz, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump and 2gb limit on windows and version 8.1.3 |
Date: | 2009-05-18 16:07:13 |
Message-ID: | 1843.1242662833@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> I think you should upgrade to 8.1.17 which likely contains the fix as
> well.
If you are thinking of this fix:
2007-02-19 10:05 mha
* src/bin/pg_dump/: pg_backup_archiver.c, pg_backup_archiver.h,
pg_backup_custom.c, pg_backup_files.c, pg_backup_tar.c, pg_dump.h
(REL8_2_STABLE), pg_backup_archiver.c, pg_backup_archiver.h,
pg_backup_custom.c, pg_backup_files.c, pg_backup_tar.c, pg_dump.h:
Fix pg_dump on win32 to properly dump files larger than 2Gb when
using binary dump formats.
it doesn't appear to have been back-patched into 8.1. However the log
message suggests a workaround: use plain-text output format.
In any case, continuing to depend on an 8.1.x server on Windows
(especially one as old as 8.1.3) is just plain stupid. We dropped
support for that release series for very good reasons. The OP needs
to get off that version --- just accepting someone's diktat that it
"can't be upgraded" is irresponsible, unless the data it contains is
of no value (which I doubt or we wouldn't be fielding this question).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Zico | 2009-05-18 16:51:41 | Re: Need help |
Previous Message | Alvaro Herrera | 2009-05-18 15:39:02 | Re: pg_dump and 2gb limit on windows and version 8.1.3 |