Horton

Re: pg_dump and large files - is this a problem?

Philip Warner <pjw@rhyme.com.au>

View thread
From: Philip Warner <pjw@rhyme.com.au>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>, Tom Lane <tgl@sss.pgh.pa.us>, Giles Lean <giles@nemeton.com.au>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2002-10-19T04:15:54Z
Lists: pgsql-hackers 
At 12:07 AM 19/10/2002 +0200, Peter Eisentraut wrote:
>Any old machine has a 4-byte off_t if you configure with
>--disable-largefile.

Thanks - done. I just dumped to a custom backup file, then dumped it do 
SQL, and compared each version (V7.2.1, 8 byte & 4 byte offsets), and they 
all looked OK. Also, the 4 byte version reads the 8 byte offset version 
correctly - although I have not checked reading > 4GB files with 4 byte 
offset, but it's not a priority for obvious reasons.

So once Giles gets back to me (Monday), I'll commit the changes.



----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|
                                  |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/