Szabó Roland wrote:
> Reading the archives I understand this is a problem of postgres version
> prior 7.1, and I'm experiencing the very same error as Steve Riley
> reported last month. I saw that the suggestion was to use 7.2, but I'm
> not sure you meant dump 7.1 database from 7.1 backend using 7.2 pg_dump.
> We have approx. 1.5 Gb of data in a 7.1 database, and would not like to
> loose it, but cannot dump it with 7.1.
Well, just to make sure you're safe, before testing anything you should
at least make a backup of the entire PostgreSQL $PGDATA directory (*with
PostgreSQL not running!*).
That way, if anything does go wrong, you can always copy this backup
into place and um.. try again (but differently of course).
Regards and best wishes,
> If this is the way to go, please
> confirm that.
> Thank you for your time.
> Roland Szabo
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
In response to
pgsql-bugs by date
|Next:||From: elein||Date: 2002-12-01 00:46:28|
|Subject: Fwd: [GENERAL] returning CHAR from C function|
|Previous:||From: Neil Conway||Date: 2002-11-28 23:14:57|
|Subject: Re: Pg_dump uses up RAM and swap space|