From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | pg_dump and large files - is this a problem? |
Date: | 2002-10-01 12:13:04 |
Message-ID: | 5.1.0.14.0.20021001221024.0467fc00@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Is it my imagination, or is there a problem with the way pg_dump uses off_t
etc. My understanding is that off_t may be 64 bits on systems with 32 bit
ints. But it looks like pg_dump writes them as 4 byte values in all cases.
It also reads them as 4 byte values. Does this seem like a problem to
anybody else?
----------------------------------------------------------------
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 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-01 13:51:12 | Re: Postgresql likes Tuesday... |
Previous Message | Guido Staub | 2002-10-01 10:25:02 | Re: current_timestamp after queries |