Re: BUG #5735: pg_upgrade thinks that it did not start the old server
От | Bruce Momjian |
---|---|
Тема | Re: BUG #5735: pg_upgrade thinks that it did not start the old server |
Дата | |
Msg-id | 201011101326.oAADQfN18338@momjian.us обсуждение исходный текст |
Ответ на | Re: BUG #5735: pg_upgrade thinks that it did not start the old server (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-bugs |
Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > >> On 10/30/2010 7:33 PM, Dave Page wrote: > >>> upgrade from a 32bit 8.3 server to a 64 bit 9.0 server, which isn't > >>> going to work without a dump/restore. With pg_upgrade, the two builds > >>> need to be from the same platform, same word size, and have the same > >>> configuration for certain settings like integer_datetimes. > > > Can anyone suggest a way pg_upgrade could detect an upgrade from a > > 32-bit to 64-bit cpu and throw an error? > > Surely it does that already, as a result of comparing pg_control > contents. Surely it does, but I didn't understand how the user able to run pg_upgrade? I see now that he failed before we completed our checks so he would have gotten an error later if he could have started his server: http://archives.postgresql.org/pgsql-bugs/2010-10/msg00282.php Thanks. Not sure why he was unable to start the old server, but we decided he couldn't use pg_upgrade anyway in his setup. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-bugs по дате отправления: