From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Organization: Dynacom Tankers Mgmt
To: pgsql-admin@postgresql.org
Subject: Re: Examining very large dumps
Date: Thu, 17 Apr 2008 08:46:24 +0300
User-Agent: KMail/1.9.7
References: <200804161235.27157.achill@matrix.gatewaynet.com>
	<200804170818.47160.achill@matrix.gatewaynet.com>
	<9879.1208409922@sss.pgh.pa.us>
In-Reply-To: <9879.1208409922@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-7"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200804170846.24713.achill@matrix.gatewaynet.com>

=D3=F4=E9=F2 Thursday 17 April 2008 08:25:22 =EF/=E7 Tom Lane =DD=E3=F1=E1=
=F8=E5:
> Achilleas Mantzios <achill@matrix.gatewaynet.com> writes:
> >> Did you make the dump using 8.3's pg_dump?
>=20
> > Yes, with 8.3.1's pg_dump (data only dump)
>=20
> 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
>=20

Ooops, now it seems i have an issue.
The whole point i went this way, was because i wanted to have a schema-only=
 dump first,
in order to clean it from everything it had to do with contrib/tsearch2, co=
ntrib/intarray, dbsize
as well as to edit the triggers (substitute tsearch2 with tsvector_update_t=
rigger), update the tsearch2 indexes
to use GIN.

So the plan was:
1) i take the schema-only dump
2) i edit the schema dump
3) i create the db
4) import _int.sql
5) import the schema
6) restore data
This procedure is kind of the official upgrade noted on http://www.sai.msu.=
su/~megera/wiki/Tsearch2_83_changes
and described on http://sql-info.de/postgresql/notes/converting-tsearch2-to=
=2D8.3.html

> http://www.postgresql.org/docs/8.3/static/populate.html
I am reading this link right away.

Any thoughts very welcome.
>=20
> 			regards, tom lane
>=20


=2D-=20
Achilleas Mantzios