AW: [HACKERS] tables > 1 gig - Mailing list pgsql-hackers

From Zeugswetter Andreas IZ5
Subject AW: [HACKERS] tables > 1 gig
Date
Msg-id 219F68D65015D011A8E000006F8590C60267B3A6@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List 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


pgsql-hackers by date:

Previous
From: David Sauer
Date:
Subject: crash if group doesn't exist (postgres 6.5, linux 2.2.10, rh 6.0)
Next
From: Wayne Piekarski
Date:
Subject: Re: [HACKERS] Update on my 6.4.2 progress