Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 0dd19ad

Browse files
committed
Add info about how to enable large-file support, so that pg_dump won't
choke at 2Gb of output. From Andrew Sullivan.
1 parent 74c8c09 commit 0dd19ad

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

doc/FAQ_Solaris

+13-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL 7.2
33
Sun Solaris specific
44
to be read in conjunction with the installation instructions
55
============================================================
6-
last updated: $Date: 2001/12/10 13:02:20 $
6+
last updated: $Date: 2002/01/18 20:56:17 $
77

88
current maintainer: Peter Eisentraut <peter_e@gmx.net>
99

@@ -13,6 +13,7 @@ Contents:
1313
1) What tools do I need to build and install PostgreSQL on Solaris?
1414
2) Why do I get problems when building with OpenSSL support?
1515
3) Why does configure complain about a failed test program?
16+
4) How do I ensure that pg_dump and pg_restore can handle files > 2 Gb?
1617

1718

1819
1) What tools do I need to build and install PostgreSQL on Solaris?
@@ -64,3 +65,14 @@ whenever you run any of the installed PostgreSQL programs.
6465

6566
Alternatively, set the environment variable LD_RUN_PATH. See the
6667
ld(1) man page for more information.
68+
69+
70+
4) How do I ensure that pg_dump and pg_restore can handle files > 2 Gb?
71+
72+
By default, gcc will build programs that only handle 32-bit file offsets.
73+
This is not a real problem for the server but can easily be trouble for
74+
pg_dump and pg_restore. Before running 'configure', set your CFLAGS variable
75+
to specify support for files with 64-bit offsets. This has been verified
76+
to work on Solaris 7:
77+
78+
CFLAGS="`getconf LFS_CFLAGS`"; export CFLAGS

0 commit comments

Comments
 (0)