Re: ERROR: could not read block 4707 of relation 1663/16384/16564: Success

From: Deniz Atak <denizatak(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: could not read block 4707 of relation 1663/16384/16564: Success
Date: 2011-08-01 06:27:44
Message-ID: CAL30GtHXFUuDc9giGx2eboS4n7CXaj1JJsb4e4o-TUWOg0uBYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Deepak, Tom thanks for answering.

Tom, we have psql 8.1.18. So you are right, this weird message is because of
the old version. I will check with my colleague about the possible reasons.
What can I do if there is a messed up table?

Regards,
Deniz

On Sat, Jul 30, 2011 at 11:45 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Deniz Atak <denizatak(at)gmail(dot)com> writes:
> > I am using postgresql on Glassfish server and I have EJB 3.0 for ORM. I
> am
> > trying to run a query in PSQL but receiving following error:
>
> > Local Exception Stack:
> > Exception [EclipseLink-4002] (Eclipse Persistence Services -
> > 2.0.0.v20091031-r5713):
> org.eclipse.persistence.exceptions.DatabaseException
> > Internal Exception: org.postgresql.util.PSQLException: ERROR: could not
> read
> > block 4707 of relation 1663/16384/16564: Success
>
> What Postgres server version is that?
>
> If it's 8.2 or older, this probably indicates a partial block at the end
> of the file. Newer versions produce a more sensible error message for
> the case, but that's just cosmetic --- the real problem is a messed-up
> table. Have you had a filesystem corruption or an out-of-disk-space
> condition on this machine?
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chetan Suttraway 2011-08-01 06:28:01 Re: PostgreSQL installation in Windows 7: Error 1935
Previous Message kalyan kumar 2011-08-01 05:35:51 Database backup to network folder