Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes

No=2C this is the first time=2C I've seen this issue.In past as well reinde=
x the tables and it works well.
BTW now I'm resetting the database to start from fresh.

Regards=2C
Mayank MittalBarco Electronics System Ltd.Mob. +91 9873437922

> From: andres@2ndquadrant.com
> To: mayank.mittal.1982@hotmail.com
> Subject: Re: [BUGS] BUG #7562: could not read block 0 in file "base/16385=
/16585": read only 0 of 8192 bytes
> Date: Fri=2C 21 Sep 2012 13:43:00 +0200
> CC: tgl@sss.pgh.pa.us=3B pgsql-bugs@postgresql.org
>=20
> On Friday=2C September 21=2C 2012 01:37:38 PM Mayank Mittal wrote:
> > As discussed with Andres on IRC=2C I tried to reproduce the issue with =
some
> > debug log enabled.In order to reproduce I fixed my already broken syste=
m
> > (index corrupted) by running REINDEX database <database_name>.Once done=
 I
> > performed the failover and now I'm getting following
> > error:[org.postgresql.util.PSQLException: ERROR: missing chunk number 0
> > for toast value 33972 in pg_toast_16582]
> Unfortunately I don't think its really a valid approach to start from an=
=20
> already corrupted database when doing this :( There might already be ling=
ering=20
> corruption causing the problem.
>=20
> Have you seen the missing chunk error before? Did you reproduce the issue=
 from=20
> a corrupted database as well before?
>=20
> Greetings=2C
>=20
> Andres
>=20
> > Regards=2C
> > Mayank MittalBarco Electronics System Ltd.Mob. +91 9873437922
> >=20
> > > Date: Fri=2C 21 Sep 2012 11:34:49 +0200
> > > From: mailings@oopsware.de
> > > To: andres@2ndquadrant.com
> > > CC: tgl@sss.pgh.pa.us=3B pgsql-bugs@postgresql.org=3B
> > > mayank.mittal.1982@hotmail.com Subject: Re: [BUGS] BUG #7562: could n=
ot
> > > read block 0 in file "base/16385/16585": read only 0 of 8192 bytes
> > >=20
> > >=20
> > >=20
> > > --On 21. September 2012 10:25:50 +0200 Andres Freund
> > >=20
> > > <andres@2ndquadrant.com> wrote:
> > > >> We had a similar issue at a customer site. The server was shut dow=
n
> > > >> for updating it from 9.1.4 to 9.1.5=2C after starting it again the=
 log
> > > >> was immediately cluttered with
> > > >=20
> > > > How was it shutdown? -m fast or -m immediate?
> > >=20
> > > -m fast
> > >=20
> > > >> ERROR:  could not read block 251 in file "base/6447890/7843708": r=
ead
> > > >> only 0 of 8192 bytes
> > > >=20
> > > > So=2C not block 0. How many blocks does the new index contain?
> > >=20
> > > 255 blocks according to its current size.
>=20
> --=20
>  Andres Freund                       http://www.2ndQuadrant.com/
>  PostgreSQL Development=2C 24x7 Support=2C Training & Services
>=20
>=20
> --=20
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
                           =