| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump large-file support > 16GB |
| Date: | 2005-03-18 21:42:32 |
| Message-ID: | 10484.1111182152@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:
> We are trying to dump a 30GB+ database using pg_dump with the --file
> option. In the beginning everything works fine, pg_dump runs and we get
> a dumpfile. But when this file becomes 16GB it disappears from the
> filesystem,
FWIW, I tried and failed to duplicate this problem on a Fedora Core 3
machine using an ext3 filesystem. I set up a dummy database that would
produce an approximately 18GB text dump and did
pg_dump big --file spare/big.dump
Seemed to work fine.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Rae | 2005-03-18 23:00:27 | Re: SMP scaling |
| Previous Message | Martijn van Oosterhout | 2005-03-18 20:05:45 | Re: Select Last n Rows Matching an Index Condition (and caches) |