Re: from 6.5 > 7.1, cannot pg_dumpall.

Patrick,

A few questions
How big is this database? (how many rows?)
Do you have more than one table?

I had a similar problem, I wrote a small program that extracted the
data to a flat file, then I pushed it back out to a new database (after I
upgraded). This only works if the schema is not very complicated.

Ted

-----Original Message-----
From: Patrick Coulombe <pcoulombe(at)mediacces(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Date: Sat, 06 Oct 2001 14:28:39 -0400
Subject: [NOVICE] from 6.5 > 7.1, cannot pg_dumpall.

> hi,
>
> i'm ready to upgrade (i know) to 7.1, but i have a big problem in my
> [PostgreSQL 6.5.3] :
>
> medias=> select * from contacts_secteurs;
> .... freeze ...
>
> medias=> select * from contacts_secteurs where contact_id =
534;
> contact_id|soussecteur_id|secteur_id
> ----------+--------------+----------
> 534| 118| 6
> 534| 114| 1
> (2 rows)
>
> so, i cannot pg_dump this database = cannot upgrade !
>
>
> the vacuum command freeze also, but wait, i just try it, and here
the
> result
> :
>
> medias=> vacuum;
> NOTICE: Rel contacts: TID 223/38: OID IS INVALID. TUPGONE 1.
> NOTICE: Rel medias_categories: TID 28/81: OID IS INVALID.
TUPGONE 0.
> NOTICE: Rel contacts_secteurs: Uninitialized page 66 - fixing
> NOTICE: Rel contacts_secteurs: Uninitialized page 67 - fixing
> ....
> NOTICE: Rel contacts_secteurs: Uninitialized page 526 - fixing
> NOTICE: Rel contacts_secteurs: Uninitialized page 527 - fixing
> NOTICE: Index contacts_secteurs_contact_id_ke: pointer to
EmptyPage
> (blk
> 527 off 169) - fixing
> .... freeze ...
>
>
> like i said in past post (no answer), i don't want to loose data in my
> upgrade, can someone try to help me to fix this, so i can be like
you
> with a
> good and stable version. if possible, this week-end, cause i have a
> vacation
> on monday.
>
> patrick
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html