"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
>
> -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:
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
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
=?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
gt;
> *From:* pgsql-admin-ow...@postgresql.org
> [mailto:pgsql-admin-ow...@postgresql.org] *On Behalf Of *Martin Povolny
> *Sent:* Tuesday, 26 October 2010 10:12 PM
> *To:* pgsql-admin@postgresql.org
> *Subject:* [ADMIN] large database: problems with pg_dump and pg_restore
>
>
Of Martin Povolny
Sent: Tuesday, 26 October 2010 10:12 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] large database: problems with pg_dump and pg_restore
Hallo,
I have some quite grave problems with dumping and restoring large databases
(>4GB of dump).
I had 5 databases, 4 dumped ok, the 5t
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
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 archiver] archive member too large
>The table contains 22+ million records which are formatted so they
>can be loaded using the psql copy command.
Well I solved the problem. It turns out that I had a programmer (me)
malfunction. My 22+ million record data had every other record
containing only a single character, a newline. My
On Fri, Mar 05, 1999 at 01:08:21PM -0700, hal Lynch wrote:
> I have a tabel I am trying to use but it won't work. Here are the
> particulars:
>
> Digital Unix 4.0E
> Postgres 6.3
> DEC 3000 400s
> 100M+ memory
> 500M swap
> 8 gig drive reserved for postgres
> With the full 22M records it s
I have a tabel I am trying to use but it won't work. Here are the
particulars:
Digital Unix 4.0E
Postgres 6.3
DEC 3000 400s
100M+ memory
500M swap
8 gig drive reserved for postgres
To create the table:
#!/bin/sh
psql sis << \__EOD__
drop table trnscpt;
create table trnscpt (
SSN
12 matches
Mail list logo
