Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-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

pgsql-novice by date

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

pgsql-general by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group