On Mon, 22 Jul 2002, Tom Lane wrote:
> Wim <wdh(at)belbone(dot)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)
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
Nigel J. Andrews
Logictree Systems Limited
In response to
pgsql-novice by date
|Next:||From: Patrick Hatcher||Date: 2002-07-22 20:38:30|
|Subject: Memory problems|
|Previous:||From: Tom Lane||Date: 2002-07-22 20:19:16|
|Subject: Re: URGENT! pg_dump doesn't work! |
pgsql-general by date
|Next:||From: Tom Lane||Date: 2002-07-22 20:31:07|
|Subject: Re: Can I use row-level locks to sequence READ COMMITTED transactions? |
|Previous:||From: Tom Lane||Date: 2002-07-22 20:26:24|
|Subject: Re: Inheritance and Update/Delete |