Re: 7.1 -> 7.3 migration timestamp problem - Mailing list pgsql-bugs

From Tom Lane
Subject Re: 7.1 -> 7.3 migration timestamp problem
Date
Msg-id 29697.1051302250@sss.pgh.pa.us
Whole thread Raw
In response to 7.1 -> 7.3 migration timestamp problem  (Joe Slag <joe.slag@walkerart.org>)
List pgsql-bugs
Joe Slag <joe.slag@walkerart.org> writes:
> redes=# update admin set email='flake' where admin_id = 1;
> FATAL:  Pre-7.3 object file made an elog() call.  Recompile.

You've got an out-of-date .so file in there somewhere.  If there are no
user-defined C functions in your database, the likely culprit is
plpgsql.so or pltcl.so or plperl.so, whichever one of those PL languages
you use.  A fairly likely bet is that the .so file is being referenced
by an absolute path that points at the old version's library directory.
Check the pg_proc.probin entry for plpgsql_call_handler, etc.  If you
need to change it, make it read something like "$libdir/plpgsql" so that
you don't get burnt again next time.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: postgres sql 7.1.1
Next
From: Tom Lane
Date:
Subject: Re: pg_dump Crashes and core dumps