pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedstill cannot connect with pgAdmin
8+ messages / 4 participants
[nested] [flat]
* still cannot connect with pgAdmin
@ 1999-12-28 16:23 Michael Meskes <meskes@postgresql.org>
0 siblings, 0 replies; 8+ messages in thread
From: Michael Meskes @ 1999-12-28 16:23 UTC (permalink / raw)
To: pgsql-interfaces
I just installed M$ MDAC and now I get further in my attempt to connect to
my PostgreSQL database. However, pgAdmin says: The selected database is not
a PostgreSQL v6.5.x system!
However, I do use 6.5.3.
On the subsequent tries I get: This database does not appear to be in teh version
6.4.x format!
The ODBC driver does work for instance from Access.
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!
^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: [INTERFACES] still cannot connect with pgAdmin
@ 2000-01-02 09:53 Dave Page <dpage@vale-housing.co.uk>
0 siblings, 0 replies; 8+ messages in thread
From: Dave Page @ 2000-01-02 09:53 UTC (permalink / raw)
To: pgsql-interfaces
> -----Original Message-----
> From: Michael Meskes [mailto:meskes@postgreSQL.org]
> Sent: 28 December 1999 16:23
> To: PostgreSQL Interfaces
> Subject: [INTERFACES] still cannot connect with pgAdmin
>
>
> I just installed M$ MDAC and now I get further in my attempt
> to connect to
> my PostgreSQL database. However, pgAdmin says: The selected
> database is not
> a PostgreSQL v6.5.x system!
>
> However, I do use 6.5.3.
>
> On the subsequent tries I get: This database does not appear
> to be in teh version
> 6.4.x format!
Because pgAdmin extracts all it's info about the connected database from the
pg_* tables rather than relying on M$ ADO or DAO, it needs to know that the
connected database is
a) PostgreSQL
b) the correct version (therefore the system tables will be of the expected
format).
During the logon process this is checked by executing:
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.
To get to the point... please execute SELECT version(); in the psql monitor
and let me know exactly what is returned.
Regards,
Dave.
--
Network & Systems Manager, The Vale Housing Association.
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
Beer can be a permanent solution, but only if you have enough of it!
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [INTERFACES] still cannot connect with pgAdmin
@ 2000-01-03 10:57 Michael Meskes <meskes@postgresql.org>
0 siblings, 1 reply; 8+ messages in thread
From: Michael Meskes @ 2000-01-03 10:57 UTC (permalink / raw)
To: pgsql-interfaces
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!
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [INTERFACES] still cannot connect with pgAdmin
@ 2000-01-03 15:12 Tom Lane <tgl@sss.pgh.pa.us>
parent: Michael Meskes <meskes@postgresql.org>
0 siblings, 1 reply; 8+ messages in thread
From: Tom Lane @ 2000-01-03 15:12 UTC (permalink / raw)
To: Michael Meskes <meskes@postgreSQL.org>; +Cc: pgsql-interfaces
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
^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: [INTERFACES] still cannot connect with pgAdmin
@ 2000-01-04 08:28 Dave Page <dpage@vale-housing.co.uk>
0 siblings, 0 replies; 8+ messages in thread
From: Dave Page @ 2000-01-04 08:28 UTC (permalink / raw)
To: pgsql-interfaces
> -----Original Message-----
> From: Michael Meskes [mailto:meskes@postgreSQL.org]
> Sent: 03 January 2000 10:57
> To: 'pgsql-interfaces@postgresql.org'
> Subject: 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=>
>
That certainly looks OK. As Tom said in another message, are you sure you
are connecting to the correct datasource? I've not heard of this problem
anywhere else and this bit of code has been in pgAdmin for a while now.
Regards,
Dave.
--
Network & Systems Manager, The Vale Housing Association.
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
Beer can be a permanent solution, but only if you have enough of it!
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: [INTERFACES] still cannot connect with pgAdmin
@ 2000-01-04 13:48 Michael Meskes <meskes@postgreSQL.org>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 8+ messages in thread
From: Michael Meskes @ 2000-01-04 13:48 UTC (permalink / raw)
To: pgsql-interfaces; +Cc: Dave Page <dpage@vale-housing.co.uk>
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!
^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: [INTERFACES] still cannot connect with pgAdmin
@ 2000-01-04 14:29 Dave Page <dpage@vale-housing.co.uk>
0 siblings, 0 replies; 8+ messages in thread
From: Dave Page @ 2000-01-04 14:29 UTC (permalink / raw)
To: pgsql-interfaces
> -----Original Message-----
> From: Michael Meskes [mailto:meskes@postgreSQL.org]
> Sent: 04 January 2000 13:48
> To: 'pgsql-interfaces@postgresql.org'
> Cc: Dave Page
> Subject: Re: [INTERFACES] still cannot connect with pgAdmin
>
>
> 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'
These options are being setup by the ODBC driver, which is also checking for
the existence of the lo type, the absence of which should not affect
pgAdmin. The ODBC driver options that pgAdmin requires (and checks) are:
ReadOnly = False
Protocol = 6.4
Under OID Options:
Show Column = True
Fake Index = True
I've never heard of any other options causing problems no matter what they
are set to (there was once a problem with Bools As Char but this should be
OK now).
To see what's going on, some log files would be useful. (Usual warning about
editting the registry goes here...) In regedit, find (or create if
necessary) a key with the path:
HKEY_CURRENT_USER\Software\Vale Software\pgAdmin
Make sure that this key contains a string value called 'Logging' with a
value of '1' (both without the quotes). If you now switch on the CommLog in
the ODBC driver, then attempt to log into pgAdmin, you should get a
C:\pgAdmin.log file and a psqlodbc_?????.log file. Please delete any
passwords from these and send them to me.
Regards,
Dave.
--
Network & Systems Manager, The Vale Housing Association.
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
Beer can be a permanent solution, but only if you have enough of it!
^ permalink raw reply [nested|flat] 8+ messages in thread
* FW: [INTERFACES] still cannot connect with pgAdmin
@ 2000-01-10 09:44 Dave Page <dpage@vale-housing.co.uk>
0 siblings, 0 replies; 8+ messages in thread
From: Dave Page @ 2000-01-10 09:44 UTC (permalink / raw)
To: pgsql-interfaces
> -----Original Message-----
> From: Michael Meskes [mailto:meskes@postgresql.org]
> Sent: 08 January 2000 13:13
> To: Dave Page
> Subject: Re: [INTERFACES] still cannot connect with pgAdmin
>
>
> On Tue, Jan 04, 2000 at 02:29:59PM -0000, Dave Page wrote:
> > ...
> > Make sure that this key contains a string value called
> 'Logging' with a
> > value of '1' (both without the quotes). If you now switch
> on the CommLog in
> > the ODBC driver, then attempt to log into pgAdmin, you should get a
> > C:\pgAdmin.log file and a psqlodbc_?????.log file. Please delete any
> > passwords from these and send them to me.
>
> Okay, did that. The log files are attached.
>
Hmmm, the psqlodbc log file doesn't look quite as I expected - the SELECT
version() isn't in it. Anyway I have beta version of 6.5.6 which has
improved logging in the code where you are having trouble. Do you mind if I
email you a zipped exe, and get you to delete the old log files, then
re-create them.
Regards,
Dave.
--
Network & Systems Manager, The Vale Housing Association.
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
Beer can be a permanent solution, but only if you have enough of it!
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2000-01-10 09:44 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-12-28 16:23 still cannot connect with pgAdmin Michael Meskes <meskes@postgresql.org>
2000-01-02 09:53 RE: [INTERFACES] still cannot connect with pgAdmin Dave Page <dpage@vale-housing.co.uk>
2000-01-03 10:57 Re: [INTERFACES] still cannot connect with pgAdmin Michael Meskes <meskes@postgresql.org>
2000-01-03 15:12 ` Tom Lane <tgl@sss.pgh.pa.us>
2000-01-04 13:48 ` Michael Meskes <meskes@postgreSQL.org>
2000-01-04 08:28 RE: [INTERFACES] still cannot connect with pgAdmin Dave Page <dpage@vale-housing.co.uk>
2000-01-04 14:29 RE: [INTERFACES] still cannot connect with pgAdmin Dave Page <dpage@vale-housing.co.uk>
2000-01-10 09:44 FW: [INTERFACES] still cannot connect with pgAdmin Dave Page <dpage@vale-housing.co.uk>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox