| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Giles Lean <giles(at)nemeton(dot)com(dot)au> |
| Subject: | Re: pg_dump and large files - is this a problem? |
| Date: | 2002-10-24 01:33:50 |
| Message-ID: | 5.1.0.14.0.20021024113025.028f3340@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 05:50 PM 23/10/2002 -0400, Bruce Momjian wrote:
>Looking at the pg_dump code, it seems the fseeks are optional in there
>anyway because it already has code to read the file sequentially rather
But there are features that are not available if it can't seek: eg. it will
not restore in a different order to that in which it was written; it will
not dump data offsets in the TOC so dump files can not be restored in
alternate orders; restore times will be large for a single table (it has to
read the entire file potentially).
----------------------------------------------------------------
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 | Bruce Momjian | 2002-10-24 01:36:35 | Re: pg_dump and large files - is this a problem? |
| Previous Message | Bruce Momjian | 2002-10-24 01:22:29 | Standalone backend doesn't read postgresql.conf |