Re: Segmentation fault (core dumped) loading data on 8.3 upgrade: undefined symbol 'pg_valid_server_encoding_id',lazy binding failed! - Mailing list pgsql-general

From Chris Paul
Subject Re: Segmentation fault (core dumped) loading data on 8.3 upgrade: undefined symbol 'pg_valid_server_encoding_id',lazy binding failed!
Date
Msg-id 47D98DD9.4070405@sentinare.com
Whole thread Raw
In response to Re: Segmentation fault (core dumped) loading data on 8.3 upgrade: undefined symbol 'pg_valid_server_encoding_id',lazy binding failed!  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane wrote:
Chris Paul <chris.paul@sentinare.com> writes: 
I exported an 8.2.6 database and am trying to load it on 8.3.0. I get 
this error:   
 
[postgres@prague:/var/postgres]$ ql -d postgres < 
bak/dump.bak                          <
/usr/local/bin/psql:/usr/local/bin/psql: undefined symbol 
'pg_valid_server_encoding_id'
lazy binding failed!   
pg_valid_server_encoding_id() is exported by 8.3's libpq, but it does
not exist in 8.2 and before.  What is evidently happening is that psql
is binding to an old copy of libpq.so.  Check your PG installation.
		regards, tom lane 
That was it! Thanks! Yeah I had the postgresql-client-8.2.6 package loaded from OpenBSD packages....

CP

--
Chris Paul
Sentinare Messaging Solutions, Inc
309 Cedar Street #72, Santa Cruz, CA 95060
email: chris.paul@sentinare.com
web: http://www.sentinare.com
phone, toll-free: +1 (877) 727-9786

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of,
or taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited.
Sentinare Messaging Solutions, Inc. is a California Corporation.

P Please don't print this e-mail, unless you really need to.


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Subplan and index usage
Next
From: "Dean Gibson (DB Administrator)"
Date:
Subject: Re: Can't rename an existnig DB because it doesn't exist???