Postgres Pro
Downloads
Home   >   mailing lists

Thread: URGENT! pg_dump doesn't work!

URGENT! pg_dump doesn't work!

From
Wim
Date:
Hello guys,

I have a problem with my postgres 7.2.1 database.
I can't perform a pg_dump one my database...
The message I get back is:

pg_dump: query to obtain list of tables failed: server closed the
connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
pg_dump failed on belbonedb_v2, exiting

Whe I connect to the database and do:

belbonedb_v2=# \dt networks

I get:

ERROR:  AllocSetFree: cannot find block containing chunk 4aee70


Can I fix this error?


Thanx!

Wim

Re: [GENERAL] URGENT! pg_dump doesn't work!

From
"Nigel J. Andrews"
Date:
On Mon, 22 Jul 2002, Wim wrote:

> Hello guys,
>
> I have a problem with my postgres 7.2.1 database.
> I can't perform a pg_dump one my database...
> The message I get back is:
>
> pg_dump: query to obtain list of tables failed: server closed the
> connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> pg_dump failed on belbonedb_v2, exiting
>
> Whe I connect to the database and do:
>
> belbonedb_v2=# \dt networks
>
> I get:
>
> ERROR:  AllocSetFree: cannot find block containing chunk 4aee70
>
>
> Can I fix this error?


Is this perhaps another of those hardware errors that seem to be turning up at
the moment?

So Wim, did you have improper shutdowns? Are you confident in your memory and
hard disk(s)?


--
Nigel J. Andrews
Director

---
Logictree Systems Limited
Computer Consultants

Re: [GENERAL] URGENT! pg_dump doesn't work!

From
Tom Lane
Date:
Wim <wdh@belbone.be> writes:
> I have a problem with my postgres 7.2.1 database.
> I can't perform a pg_dump one my database...
> The message I get back is:

Odd.  I am thinking this might be a corrupted-data problem.

If you are lucky, the corruption is in an index, and you can fix it
by rebuilding the system indexes.  Read the REINDEX reference page
(carefully, it's a convoluted procedure)

            regards, tom lane

Re: [GENERAL] URGENT! pg_dump doesn't work!

From
"Nigel J. Andrews"
Date:
On Mon, 22 Jul 2002, Tom Lane wrote:

> Wim <wdh@belbone.be> writes:
> > I have a problem with my postgres 7.2.1 database.
> > I can't perform a pg_dump one my database...
> > The message I get back is:
>
> Odd.  I am thinking this might be a corrupted-data problem.
>
> If you are lucky, the corruption is in an index, and you can fix it
> by rebuilding the system indexes.  Read the REINDEX reference page
> (carefully, it's a convoluted procedure)

Tom,

That's why I went down the hardware question. Given the error reported by Wim
though seems to be a memory allocation, actually freeing, fault would data
corruption in any persistent storage object be suspect?

I suppose it worth checking that the error persists across a backend
restart. Wim?


--
Nigel J. Andrews
Director

---
Logictree Systems Limited
Computer Consultants

Re: [GENERAL] URGENT! pg_dump doesn't work!

From
Tom Lane
Date:
"Nigel J. Andrews" <nandrews@investsystems.co.uk> writes:
> That's why I went down the hardware question. Given the error reported by Wim
> though seems to be a memory allocation, actually freeing, fault would data
> corruption in any persistent storage object be suspect?

I am thinking a corrupted length word in a varlena data item (text,
varchar, array, etc) might possibly lead to that sort of error.
It's just an educated guess though.

            regards, tom lane