I was able to dump the corrupt database using Postgres 8.1. The pg_dump utility of 7.1 stops on errors.
Are there issues in using pg_dump for Postgres 8.1 to a database created in Postgres 7.1?
After dumping the database. I tried to load it on Postgres 8.1. I encountered errors on some database tables. Some lines on the file are empty (a blank record or a corrupt record?). Before the said lines, there was a "\M". What does "\M" stand for?
Thanks in advance.
Regards,
Jonathan
On 8/4/06, Jaime Casanova <systemguards@xxxxxxxxx> wrote:
On 8/3/06, Jonathan Vallar <bamvallar.db@xxxxxxxxx> wrote:
> Hi!
>
> I have a corrupt database that runs on Postgres 7.1.2. I was able to repair
> the database where I can now connect to the database and do queries.
>
> I have a migration plan to transfer my database to a Postgres 8.1. I
> encountered problems when I was dumping the database. Postgres 7.1 reported:
> getTables(): SELECT (funcname) for trigger trig_mis_t_ins returned 0 tuples.
> Expected 1.
>
> The trig_mis_t_ins trigger is no longer found on the database but it is
> still listed at the database. With this, I assume the database is corrupt.
>
> Would my problems go away if I dump it on postgres 8?
>
> Thanks.
>
> Regards,
>
> Jonathan
>
the better yu can do is try to dump the database with the 8.1's
pg_dump... but i don't know what problems can be (or if there is a
problem doing that)...
the better we can do is to wish you luck, your version is obsolete and
unsupported from some time ago...
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook
