From: Tom Lane <tgl@sss.pgh.pa.us>
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Examining very large dumps
Date: Thu, 17 Apr 2008 01:25:22 -0400
Message-ID: <9879.1208409922@sss.pgh.pa.us> (raw)
In-Reply-To: <200804170818.47160.achill@matrix.gatewaynet.com>
References: <200804161235.27157.achill@matrix.gatewaynet.com>
<8622.1208359420@sss.pgh.pa.us>
<200804170818.47160.achill@matrix.gatewaynet.com>
Achilleas Mantzios <achill@matrix.gatewaynet.com> writes:
>> Did you make the dump using 8.3's pg_dump?
> Yes, with 8.3.1's pg_dump (data only dump)
That would be your problem. *Don't* use a data-only dump, it
lobotomizes all intelligence in the system and leaves it up to you
to deal with foreign-key ordering issues. There are lots of
performance arguments against that as well. See the advice at
http://www.postgresql.org/docs/8.3/static/populate.html
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, achill@matrix.gatewaynet.com
Subject: Re: Examining very large dumps
In-Reply-To: <9879.1208409922@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox