Re: [ADMIN] large database: problems with pg_dump and pg_restore

2010-10-31 Thread Dimitri Fontaine
"Jehan-Guillaume (ioguix) de Rorthais" writes: > If you can spend some more time using -Fc, then you'll be able to play > with -l and -L switches of pg_restore to optionally decide what should > be restored or not (with more control than -n, -t, etc, think about > excluding slony stuffs as instanc

Re: [ADMIN] large database: problems with pg_dump and pg_restore

2010-10-27 Thread Jehan-Guillaume (ioguix) de Rorthais
> > -Original Message- > From: pgsql-admin-ow...@postgresql.org > [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Jehan-Guillaume > (ioguix) de Rorthais > Sent: Tuesday, October 26, 2010 4:22 PM > To: Martin Povolny > Cc: pgsql-admin@postgresql.org > Subject:

[ADMIN] Re: [ADMIN] large database: problems with pg_dump and pg_restore

2010-10-27 Thread Martin Povolny
27.10.2010 t...@sss.pgh.pa.us napsal(a): > =?utf-8?Q?Martin_Povolny?= writes: >> I had 5 databases, 4 dumped ok, the 5th, the largest failed dumping: I >> was unable to >> make a dump in the default 'tar' format. I got this message: >> pg_dump: [tar archiver] archive member too large for tar forma

Re: [ADMIN] large database: problems with pg_dump and pg_restore

2010-10-26 Thread mark
ubject: Re: [ADMIN] large database: problems with pg_dump and pg_restore -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Or even compress AND split it ! pg_dump -Fc dbname | split -b 1G - dump_dbname and restore: cat dump_dbname* | pg_restore -d dbname or cat dump_dbname* | pg_restore | psql

Re: [ADMIN] large database: problems with pg_dump and pg_restore

2010-10-26 Thread Tom Lane
=?utf-8?Q?Martin_Povolny?= writes: > I had 5 databases, 4 dumped ok, the 5th, the largest failed dumping: I was > unable to > make a dump in the default 'tar' format. I got this message: > pg_dump: [tar archiver] archive member too large for tar format This is expected: tar format has a document

Re: [ADMIN] large database: problems with pg_dump and pg_restore

2010-10-26 Thread Jehan-Guillaume (ioguix) de Rorthais
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Or even compress AND split it ! pg_dump -Fc dbname | split -b 1G - dump_dbname and restore: cat dump_dbname* | pg_restore -d dbname or cat dump_dbname* | pg_restore | psql dbname Le 26/10/2010 23:51, Samuel Stearns a écrit : > You can also try

Re: [ADMIN] large database: problems with pg_dump and pg_restore

2010-10-26 Thread Samuel Stearns
You can also try piping the dump through gzip and then restoring using cat: pg_dumpall | gzip > db.out-`date +\%Y\%m\%d\%H`.gz cat db.out-`date +\%Y\%m\%d\%H`.gz | gunzip | psql template1 Sam From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Martin

Re: [ADMIN] large database: problems with pg_dump and pg_restore

2010-10-26 Thread lst_hoe02
Zitat von Martin Povolny : Hallo, I have some quite grave problems with dumping and restoring large databases (>4GB of dump). I had 5 databases, 4 dumped ok, the 5th, the largest failed dumping: I was unable to make a dump in the default 'tar' format. I got this message: pg_dump: [tar a