| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | Joe Slag <joe(dot)slag(at)walkerart(dot)org> | 
| Cc: | pgsql-bugs(at)postgresql(dot)org | 
| Subject: | Re: 7.1 -> 7.3 migration timestamp problem | 
| Date: | 2003-04-25 20:24:10 | 
| Message-ID: | 29697.1051302250@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-bugs | 
Joe Slag <joe(dot)slag(at)walkerart(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-04-25 20:26:40 | Re: pg_dump Crashes and core dumps | 
| Previous Message | Tom Lane | 2003-04-25 20:17:48 | Re: postgres sql 7.1.1 |