I have a 9.1.3 instance (Redhat 5) with some unlogged tables. I did the
following steps:
1. pg_basebackup to create a base.tar
2. Used the base.tar plus the WALs required by the backup to restore the db
to another 9.1.3 server. This went fine, except at the end of the recovery
I got this error (file exists).
7740 2013-03-28 09:44:16 MDT [2013-03-28 09:38:43 MDT] [29] LOG: archive
recovery complete
7752 2013-03-28 09:44:16 MDT [2013-03-28 09:38:48 MDT] [1] LOG:
checkpoint starting: end-of-recovery immediate wait
7752 2013-03-28 09:44:25 MDT [2013-03-28 09:38:48 MDT] [2] LOG:
checkpoint complete: wrote 8213 buffers (1.6%); 0 transaction log file(s)
added, 0 removed, 0 recycled; write=7.361 s, sync=1.563 s, total=8.992 s;
sync files=2492, longest=0.069 s, average=0.000 s
*7740 2013-03-28 09:44:25 MDT [2013-03-28 09:38:43 MDT] [30] FATAL:
could not create file "base/886355/29806058": File exists*
7737 2013-03-28 09:44:25 MDT [2013-03-28 09:38:42 MDT] [1] LOG: startup
process (PID 7740) exited with exit code 1
7737 2013-03-28 09:44:25 MDT [2013-03-28 09:38:42 MDT] [2] LOG:
terminating any other active server processes
In a minute, started up again, and it came up without errors, and we ran for
a couple of days with no errors noted.
3. I then did a pg_upgrade to 9.2.3. All went well, until...
Linking user relation files
/var/lib/pgsql/9.1/data/base/16388/15963579
error while creating link for relation "stage.classification"
("/var/lib/pgsql/9.1/data/base/16388/15963579" to
"/var/lib/pgsql/9.2/data/base/16433/15963579"): No such file or directory
Failure, exiting
I checked and it's true, the file does not exist. Now I can't proceed and
the 9.1 data is not usable. I looked at the original database from which
the copy was made, and the relation in question is an UNLOGGED table. This
suggests that there's some consideration for binary recovery. I don't care
about the unlogged table data, but I do need the table definition. We use a
few dozen unlogged tables. Any ideas?
Thanks,
Gordon
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Upgrade-from-9-1-to-9-2-fails-due-to-unlogged-table-tp5750194.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.