Re: URGENT! pg_dump doesn't work!

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
Cc: Wim <wdh(at)belbone(dot)be>, pgsql-novice(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: URGENT! pg_dump doesn't work!
Date: 2002-07-23 15:30:46
Message-ID: 4941.1027438246@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-novice

"Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Josh Berkus 2002-07-23 15:37:23 Re: Editor for pgsql
Previous Message Andrew Sullivan 2002-07-23 15:18:01 Re: No command history in psql

Browse pgsql-novice by date

  From Date Subject
Next Message Molenda, Mark P 2002-07-23 19:06:52 large table and temp space.
Previous Message Tuomas Vanhanen 2002-07-23 14:35:24 Security, IP and username restrictions