From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump large-file support > 16GB |
Date: | 2005-03-21 15:16:14 |
Message-ID: | 19680.1111418174@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> writes:
> Do you use any spesial option when you compile pg_dump, or in the
> program that could influence how the program behaves and can help me to
> reproduce the problem?
In a Linux system we'll add "-D_GNU_SOURCE" to the compile command line.
Also, pg_config.h sets some #define's that might affect things,
particularly "#define _FILE_OFFSET_BITS 64". I see you did both of
those in your test, but you might want to review pg_config.h to see if
anything else looks promising.
Another line of thought is that there is something broken about the
particular build of Postgres that you are using (eg it was affected by a
compiler bug). You might try building from source, or grabbing the src
RPM and rebuilding from that, and confirming the bug is still there ---
and if so, back off the CFLAGS to minimal optimization and see if it
changes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hrishikesh Deshmukh | 2005-03-21 15:29:51 | Time Stamp |
Previous Message | Harald Fuchs | 2005-03-21 14:26:45 | Re: no IF - am I missing something ? |