From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Organization: Dynacom Tankers Mgmt
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: pgsql 8.3.3 "Invalid page header" leads to "FATAL: segment too
	big"
User-Agent: KMail/1.9.7
References: <201004221516.08729.achill@matrix.gatewaynet.com>
	<671.1271947353@sss.pgh.pa.us>
In-Reply-To: <671.1271947353@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Disposition: inline
Date: Thu, 22 Apr 2010 17:25:20 +0200
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201004221825.20609.achill@matrix.gatewaynet.com>

=CE=A3=CF=84=CE=B9=CF=82 Thursday 22 April 2010 17:42:33 =CE=B3=CF=81=CE=AC=
=CF=88=CE=B1=CF=84=CE=B5:
> Achilleas Mantzios <achill@matrix.gatewaynet.com> writes:
> > Then i did: (as i said i do not need the contents of msgsource - yet th=
e contents of msgno are vital)
> > dd if=3D/dev/zero of=3D/usr/local/var/lib/pgsql/data/base/125714957/125=
716013 seek=3D672720 bs=3D8192 count=3D1=20
>=20
> > However, after that, unfortunately i get constant postgresql server res=
tarts with:
> > FATAL:  segment too big
>=20
> You got the dd command wrong and made the file size change to something
> it shouldn't be.  I think you can use dd to truncate the file back to
> what it should be (ie, exactly 1GB) but haven't had enough caffeine to
> remember exactly how.
>=20
> I think the underlying error is that block 672720 isn't going to be in
> the first segment of the table --- you need to be zeroing something in
> one of the other segments...

Great, thanx a lot,
any idea about the naming of the files of those other segments?

>=20
> 			regards, tom lane
>=20


=2D-=20
Achilleas Mantzios