From: | Gordon Shannon <gordo169(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Upgrade from 9.1 to 9.2 fails due to unlogged table? |
Date: | 2013-03-30 23:08:04 |
Message-ID: | 1364684884565-5750207.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I repeated the entire process, and I have a few clarifications.
When I said the db seemed fine after the restore, I was wrong. I could do a
\d on an unlogged table, but when I selected count(*) from any, that
resulted in an error like "could not open file "base/16388/15963587": No
such file or directory". So the database was definitely not happy after the
restore.
Also, I was wrong when I said I "couldn't go back" after the failed upgrade.
I read the output again, and yes I was able to restart 9.1 after renaming
pg_control.old.
Next, I tried dropping and recreating all my UNLOGGED tables, as logged
tables. On my first try, I forgot a few tables, and the pg_upgrade error
this time was:
Linking user relation files
/var/lib/pgsql/9.1/data/base/16389/29807980
error while creating link for relation "pg_toast.pg_toast_15949256_index"
("/var/lib/pgsql/9.1/data/base/16389/29807980" to
"/var/lib/pgsql/9.2/data/base/16434/15949261"): No such file or directory
Failure, exiting
I realized my mistake, and recreated the remaining unlogged tables. After
that the pg_upgrade worked perfectly.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Upgrade-from-9-1-to-9-2-fails-due-to-unlogged-table-tp5750194p5750207.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | ajmcello | 2013-03-31 03:40:34 | Re: Regular function |
Previous Message | Alvaro Herrera | 2013-03-30 21:44:44 | Re: Money casting too liberal? |