| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Giles Lean <giles(at)nemeton(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump and large files - is this a problem? |
| Date: | 2002-10-18 22:07:07 |
| Message-ID: | Pine.LNX.4.44.0210181836540.928-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Philip Warner writes:
>
> I have made the changes to pg_dump and verified that (a) it reads old
> files, (b) it handles 8 byte offsets, and (c) it dumps & seems to restore
> (at least to /dev/null).
>
> I don't have a lot of options for testing it - should I just apply the
> changes and wait for the problems, or can someone offer a bigendian machine
> and/or a 4 byte off_t machine?
Any old machine has a 4-byte off_t if you configure with
--disable-largefile. This could be a neat way to test: Make two
installations configured different ways and move data back and forth
between them until it changes. ;-)
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-10-18 22:08:25 | Re: ECPG and bison |
| Previous Message | Peter Eisentraut | 2002-10-18 22:06:32 | Re: PL/Perl and Perl 5.8 |