Обсуждение: Re: Trouble with Connection
ODBC Driver Version 7.02.00.01 I think the server engine is Postgres95. The error message I get is when trying to open the database in Microsoft Query: "WARN:=for int4 and oid using DEFINE OPERATOR" and then "Couldn't read this file". My apologies, I wasn't sure which log file to include. My guess is that it is due to a version mismatch with the driver and the older version of the DB. Do you know where I can get an older driver (for Windows) that would allow me to migrate this data to another system (i.e. newer version of PostgreSQL)? Regards, Robby Tanner B.Sc. (EE), B.Sc. (Cmpt. Sci) Controls Engineer Canadian Light Source University of Saskatchewan 101 Perimeter Road Saskatoon, Saskatchewan Canada S7N 0X4 Ph: (306) 657-3582 Fax: (306) 657-3535 http://www.lightsource.ca
Вложения
Robby Tanner wrote:
>
> ODBC Driver Version 7.02.00.01
>
> I think the server engine is Postgres95.
The current odbc driver doesn't support Postgres95.
Unfortunately I don't know if there was such a driver
and don't know Postgres95 itself.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> Robby Tanner wrote:
>> I think the server engine is Postgres95.
> The current odbc driver doesn't support Postgres95.
I'm amazed there are still any running copies of Postgres95. Are you
holding it till the Smithsonian comes for it? :-)
Anyway, you should certainly not think in terms of using ODBC for an
upgrade. pg_dump, install new version, run pg_dump script is the thing
to do. Be advised that Postgres95 -> current is a large jump. There is
probably no hope that your dump script will load without manual editing.
(If the PG95 pg_dump supports dumping schema and data separately, I'd
advise doing it that way, since your editing will probably all be of
the schema declarations.)
regards, tom lane