Date: Wed, 16 Apr 2008 12:07:43 +0200
From: Tino Schwarze <postgresql@tisc.de>
To: pgsql-admin@postgresql.org
Subject: Re: Examining very large dumps
Message-ID: <20080416100743.GD31097@easy2.in-chemnitz.de>
References: <200804161235.27157.achill@matrix.gatewaynet.com>
	<20080416095245.GC31097@easy2.in-chemnitz.de>
	<200804161258.30731.achill@matrix.gatewaynet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200804161258.30731.achill@matrix.gatewaynet.com>
User-Agent: Mutt/1.5.13 (2006-08-11)

On Wed, Apr 16, 2008 at 12:58:29PM +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, COPY), i got some ugly ERRORs denoting foreign key constraint
> > > violations.  Since the dump is 35 Gbytes, i'd like your advice for
> > > examining, editing, 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.
> > 
> > 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 some form
> of grep.

less will try to count the number of lines. You may savely interrupt
this by CTRL-C.

> 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.

I'm afraid that would be sed in this case. At least I don't know of any
special large text file editor. After all, if you need to search,
there's almost no way around searching through the whole 35 GB.

Tino.

-- 
„What we resist, persists.” (Zen saying)

www.craniosacralzentrum.de
www.forteego.de