From: | Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> |
---|---|
To: | "'gjerde(at)icebox(dot)org'" <gjerde(at)icebox(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | AW: [HACKERS] tables > 1 gig |
Date: | 1999-06-21 07:46:51 |
Message-ID: | 219F68D65015D011A8E000006F8590C60267B3A6@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I suppose it wouldn't be overly hard to have pg_dump/pg_dumpall do
> something similar to what postgres does with segments. I haven't looked
> at it yet however, so I can't say for sure.
>
I would not integrate such functionality into pg_dump, since it is not
necessary.
A good thing though would be a little HOWTO on splitting and/or compressing
pg_dump output.
The principle is:
backup:
mkfifo tapepipe
( gzip --fast -c < tapepipe | split -b512m - database.dump.gz. ) &
pg_dump -f tapepipe regression
rm tapepipe
restore:
createdb regression
cat database.dump.gz.* | gzip -cd | psql regression
Instead of gzip you could use a faster compressor like lzop, but you get the
idea :-)
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 1999-06-21 08:17:10 | Re: [HACKERS] BSD vs. GPL |
Previous Message | David Sauer | 1999-06-21 06:24:32 | crash if group doesn't exist (postgres 6.5, linux 2.2.10, rh 6.0) |