Re: Can't get ECPG to connect (was Re: Urgen help required)

Jas, you might need to check the uplink and downlink time of your network
router.
Also,check the postgresql.conf file to see various timeouts there. Comment
all the timeouts to set them to infinity so that your Unix tools server
keeps trying connecting to the Postgres server.
Also, check if you closed the client socket in ur postgres database. This
might be one of the reasons of the whole fuss.

*Also, your "Urgent help required" subject line is more than enough to
catch an eye. I don't think it needs any amendment.*
Anyways, do let me know if you need any further help. I'll be glad to assist
you with this.
You are working on the side effects of postgres and its quite obvious that
you'll face all such problems. Keep your cools.

Regards,
~Harpreet.

On 10/18/06, Bill Moran <wmoran(at)collaborativefusion(dot)com> wrote:
>
> In response to "J S B" <jsbali(at)gmail(dot)com>:
>
> > Hi,
> > I have the following scenario:-
> >
> > 1. There's a function in the postgres datbase that when executed calls a
> > shared object (dynamically loaded).
> > 2. The shared object is a Client (made using socket library) which
> connects
> > to a server (coded again using socket library) hosted on some other
> machine.
> > 3. This server when invoked through the postgres function described
> above
> > has an ECPG code in it that gets executed after a successful write back
> to
> > the client, which inserts a record in a table in the postgres database.
> >
> > I use ECPGdebug in the begening of the server code file to see the state
> of
> > affairs with the ECPG code and it always raises -402 sqlcode which means
> the
> > connection attempt to the database did not succeed.
> >
> > All firewalls in the datbase server and this machine wherein my socket
> > server is running are disabled.
> > Other function calls from this machine to my database machine are
> working
> > fine.
> >
> > Also, my postgres function is able to establish connection with the this
> > outside deamon (that i refer to as server coded using socket library).
> > Just the ECPG calls from this deamon back to postgres database are not
> > successful.
> >
> > Any kind of help would be highly appreciated.
>
> How about help posting a better question.
>
> First off, use a descriptive subject. Notice how I've improved this for
> you.
>
> Secondly, always cut/paste exact error messages. There are some people
> who will quickly know exactly what is wrong if they see the whole error
> message.
>
> Thirdly, have a look in the PostgreSQL server logs. If there's nothing
> telling there, bump up the authentication/connection debugging in
> postgresql.conf and try again. If you get messages but aren't sure what
> they mean, post them to the list.
>
> Fourthly, be more specific. It would be worthwhile to show the snippit
> of code that connects, so people know whether you're using IP sockets are
> unix domain sockets.
>
> Fifthly, are you using unix domain sockets or IP sockets? And are the
> appropriate permissions in pg_hba.conf?
>
> --
> Bill Moran
> Collaborative Fusion Inc.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>