From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | RE: [INTERFACES] still cannot connect with pgAdmin |
Date: | 2000-01-04 14:29:59 |
Message-ID: | 8568FC767B4AD311AC33006097BCD3D60915EC@woody.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
> -----Original Message-----
> From: Michael Meskes [mailto:meskes(at)postgreSQL(dot)org]
> Sent: 04 January 2000 13:48
> To: 'pgsql-interfaces(at)postgresql(dot)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!
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-01-04 17:45:59 | escaping characters ... |
Previous Message | Michael Meskes | 2000-01-04 13:48:25 | Re: [INTERFACES] still cannot connect with pgAdmin |