Обсуждение: Re: [INTERFACES] still cannot connect with pgAdmin

On Sun, Jan 02, 2000 at 09:53:12AM -0000, Dave Page wrote:
> SELECT version()
> 
> To work correctly, the major and minor version numbers of the database
> should be the same as pgAdmin's (eg. 6.5.x PostgreSQL will work with 6.5.x
> pgAdmin). In the case of pgAdmin 6.5.x, it is looking at the first 14
> characters returned by the SELECT which are expected to be:
> 
> PostgreSQL 6.5
> 
> If they are not, then you get the error you've experienced.

But checking with psql I get
timesheet=> select version();
version
-------------------------------------------------------------
PostgreSQL 6.5.3 on i686-pc-linux-gnu, compiled by gcc 2.95.2
(1 row)
timesheet=> 

Michael
-- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael@Fam-Meskes.De           | Use PostgreSQL!

Michael Meskes <meskes@postgreSQL.org> writes:
> On Sun, Jan 02, 2000 at 09:53:12AM -0000, Dave Page wrote:
>> To work correctly, the major and minor version numbers of the database
>> should be the same as pgAdmin's (eg. 6.5.x PostgreSQL will work with 6.5.x
>> pgAdmin). In the case of pgAdmin 6.5.x, it is looking at the first 14
>> characters returned by the SELECT which are expected to be:
>> 
>> PostgreSQL 6.5
>> 
>> If they are not, then you get the error you've experienced.

> But checking with psql I get
> timesheet=> select version();
> version
> -------------------------------------------------------------
> PostgreSQL 6.5.3 on i686-pc-linux-gnu, compiled by gcc 2.95.2
> (1 row)
> timesheet=> 

Before you spend too much time digging for a bug in pgAdmin,
check the possibility that it's connecting to some other database
server than you think it is.  Just a thought...
        regards, tom lane

On Mon, Jan 03, 2000 at 10:12:14AM -0500, Tom Lane wrote:
> Before you spend too much time digging for a bug in pgAdmin,
> check the possibility that it's connecting to some other database
> server than you think it is.  Just a thought...

Unfortunately this is not the problem. I did start the postmaster with
debugging on and see pgAdmin connecting to it. However, I do not see it
asking 'select VERSION()'. 

The statements I get through debugging output are:

set DateStyle to 'ISO'
set ksqo to 'ON'
select oid from pg_type where typname='lo'

The type 'lo' however does not exists in this database, i.e. there is no oid
returned. But this hardly looks like a bug in my setup.

Also I only have one connection defined on my M$ machine and with M$ Access
I can see and change all my data.

Is it possible that my ODBC setting are insufficient? I remeber pgAccess
asking for some driver settings I had to enable. But then I did enable them.

Michael
-- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael@Fam-Meskes.De           | Use PostgreSQL!