From: | Seann Reed <reedseannm(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | cannot connect to database through ECPG but can through psql |
Date: | 2015-06-04 15:37:37 |
Message-ID: | CAEGv3bB9eu183kMHY7iB+paAzNrT6s0nbFBsPDgJ9bt=2=QCsw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm a relative newbie to Postgres but I've asked a few colleagues about
this problem without a solution, so I'm hoping someone on the list serve
can help.
The problem arose when I move to an upgraded operating system, an upgraded
version of Postgres, and when I dump a database out of the old machine and
restore it on a new machine.
Old: RedHat 5.9, Postgres 8.1.23
New: RedHat 6.6, Postgres 9.2
Everything worked fine with the old setup. With the new setup, I can
access my database through psql command-line. However, I have a compiled
program called 'Shefdecode' that makes queries to the database through ECPG
and this program cannot access the database. I get errors:
"Postgres error -220" and
"SQL STATE = 08003" (User manual says this means "The program tried to
access a connection that does not exist.")
Although I don't have the source for the Shefdecode program, I know it uses
the environment variables PGUSER and PGHOST and also gets passed the
database name. I've checked to make sure these are correct.
What else should I look for to try to determine the cause of this error?
Any ideas would be greatly appreciated.
Seann
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2015-06-04 16:04:00 | Re: cannot connect to database through ECPG but can through psql |
Previous Message | Marc Mamin | 2015-06-04 15:08:20 | Re: Row visibility issue with consecutive triggers, one being DEFERRED |