Few weeks ago I had exactly same issue during upgrade from 3.8.13 to
4.0.10.
Because I didn’t find root cause of this issue I had to install PG 9.1
temporarily (on other virtual machine) then import DB from PG 9.2.x,
upgrade and then export back to 9.2.x.
Best regards,
Pavel
Pavel Šidlo
LinuxBox.cz, s.r.o.
28. října 168, 709 00 Ostrava
tel.: +420 591 166 234
mob.: +420 737 238 334
web: www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
|------------>
| Od: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|saxmad g.mason@fairfx.com |
--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Komu: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|rt-users@lists.bestpractical.com, |
--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Datum: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|05/17/2013 18:05 |
--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Předmět: |
|------------>
--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [rt-users] Problems upgrading from 3.9.3 |
--------------------------------------------------------------------------------------------------------------------------------------------------|
Hmm, so is there a workaround/fix for this from either side, or is 9.2 not
really supported fully ? I have had 9.2 running fine on a completely fresh
install of RT 4.0.7. Would it better to go back to PG 9.1 to get this
upgrade sorted ?
Thanks for all the help so far …
View this message in context:
http://requesttracker.8502.n7.nabble.com/Problems-upgrading-from-3-9-3-tp53543p53909.html
RT Training in Seattle, June 19-20: http://bestpractical.com/training
Hmm, so is there a workaround/fix for this from either side, or is 9.2 not
really supported fully ? I have had 9.2 running fine on a completely fresh
install of RT 4.0.7. Would it better to go back to PG 9.1 to get this
upgrade sorted ?
Thanks for all the help so far …
I’ve checked DBD::Pg’s git repository. Problem is actually in that module
and you’re lucky. It’s been fixed in 2.19.3 (the latest from the CPAN), but
was not mentioned in the changelog. Upgrade the module and try again.
View this message in context:
http://requesttracker.8502.n7.nabble.com/Problems-upgrading-from-3-9-3-tp53543p53909.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.
–
RT Training in Seattle, June 19-20: http://bestpractical.com/training
Best regards, Ruslan.
I’m on Postgres 9.2 on Debian Wheezy.
So is this a Postgres issue or an RT upgrade issue ?
Both. RT uses something that is deleted. Pg deleted something that is
used
by software.
More precisely, they removed something from a system catalog – the
spclocation column in the description of tablespaces – which was
statically set at tablespace creation time and could be invalidated
silently by an innocent & plausible admin oversight, and replaced the
functionality with something else – the pg_tablespace_location()
function – which provides the same information determined dynamically
at runtime. Note that the internal structure of Pg system catalogs is an
area where software developers and sysadmins should expect to find
change across major releases and this was a well-documented change with
public discussion before it was made and during the 9.2 beta period.
IOW: A documented change in Pg 9.2 fixed a design error that needed
fixing.
The OPERATIONALLY focused answer is simpler: You must update the Perl
module DBD::Pg to v2.19.3 to get compatibility with PostgreSQL 9.2 and
later.
Thanks to all, but especially Ruslan.
Upgrading that perl module to the latest version did indeed fix the issue
and I was able to do a full migration from 3.6.7 to 4.0.7 on Postgresql 9.2.
View this message in context: http://requesttracker.8502.n7.nabble.com/Problems-upgrading-from-3-9-3-tp53543p54053.html
Thanks to all, but especially Ruslan.
Upgrading that perl module to the latest version did indeed fix the issue
and I was able to do a full migration from 3.6.7 to 4.0.7 on Postgresql
9.2.
Good to know. We’re planning to updated upgrade scripts so they throw more
meaningful errors in this situation. We can not bump dependency for all
users on Pg.
–
View this message in context:
http://requesttracker.8502.n7.nabble.com/Problems-upgrading-from-3-9-3-tp53543p54053.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.
–
RT Training in Seattle, June 19-20: http://bestpractical.com/training
Best regards, Ruslan.