Upgrade from Postgres 8.2.4 to 8.3.5

"Nykolyn, Andrew P (AS)" <andrew.nykolyn@ngc.com> writes:

I have successfully installed 8.3.5 as a fresh install on a Redhat 4.5
machine. Now I try to upgrade another Redhat 4.5 machine with an
existing 8.2.4 install and the "make check" fails all tests. When I
look at the results file for each type being tested I see the same error
indicating that there is an undefined symbol:
pg_valid_server_encoding_id and the test does not get run. Any ideas on
what I might be missing or have to change? Thanks much.

Sounds like you are trying to use an 8.3 client program with an 8.2
version of libpq.so.

regards, tom lane

"Nykolyn, Andrew P (AS)" <andrew.nykolyn@ngc.com> writes:

I have successfully installed 8.3.5 as a fresh install on a Redhat 4.5

machine. Now I try to upgrade another Redhat 4.5 machine with an
existing 8.2.4 install and the "make check" fails all tests. When I
look at the results file for each type being tested I see the same
error indicating that there is an undefined symbol:
pg_valid_server_encoding_id and the test does not get run. Any ideas
on what I might be missing or have to change? Thanks much.

Sounds like you are trying to use an 8.3 client program with an 8.2
version of libpq.so.

regards, tom lane

Why would the new install of 8.3.5 be using an 8.2 version of libpq.so
and how could I insure using the correct or 8.3 version of libpq.so for
the install? Thanks.

Andy Nykolyn

"Nykolyn, Andrew P (AS)" <andrew.nykolyn@ngc.com> writes:

Sounds like you are trying to use an 8.3 client program with an 8.2
version of libpq.so.

Why would the new install of 8.3.5 be using an 8.2 version of libpq.so

It's the same major version number, ie libpq.so.5, so if you'd failed to
replace 8.2 with 8.3 then the clients would try to use the 8.2 version.
Which would work fine for 8.2 clients and not so much for 8.3 clients,
because the 8.3 version exports additional functions.

regards, tom lane