From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Organization: Dynacom Tankers Mgmt
To: pgsql-admin@postgresql.org
Subject: Re: Examining very large dumps
Date: Wed, 16 Apr 2008 12:58:29 +0300
User-Agent: KMail/1.9.7
References: <200804161235.27157.achill@matrix.gatewaynet.com>
	<20080416095245.GC31097@easy2.in-chemnitz.de>
In-Reply-To: <20080416095245.GC31097@easy2.in-chemnitz.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-7"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200804161258.30731.achill@matrix.gatewaynet.com>

=D3=F4=E9=F2 Wednesday 16 April 2008 12:52:45 =EF/=E7 Tino Schwarze =DD=E3=
=F1=E1=F8=E5:
> On Wed, Apr 16, 2008 at 12:35:26PM +0300, Achilleas Mantzios wrote:
> > Hi, i just started the process of migrating from 7.4 to 8.3.1.
> > On restoring, apart from the easily explainable ERRORs (both in DDL, CO=
PY), i got some ugly ERRORs
> > denoting foreign key constraint violations.
> > Since the dump is 35 Gbytes, i'd like your advice for examining, editin=
g, extracting portions of large dumps,
> > in order to find the cause of the problem. vim (linux), vi (FreeBSD) or=
 any other unix editor i tried, could not handle the
> > volume.
>=20
> Do you have a plain text dump or a compressed archive? Try using less
> for a first view, then extract things with grep or alter with sed.
Its a text dump. however less, tail, head seem dead slow, i'll try with som=
e form
of grep.
I'd like to know if there is some kind of more efficient editor for viewing=
, searching
very large text files, searching by lineno or content.
>=20
> HTH,
>=20
> Tino.
>=20
> --=20
> =E2=80=9EWhat we resist, persists.=E2=80=9D (Zen saying)
>=20
> www.craniosacralzentrum.de
> www.forteego.de
>=20


=2D-=20
Achilleas Mantzios