Re[2]: libpq PQstatus problem

____________________Forward Header_____________________
Subject:    Re[2]: [INTERFACES] libpq PQstatus problem
Author: Philip Howell
Date:       14/03/01 3:32 PM

Sorry,
I should have stressed that the postgreSQL  server and the client test program
are on different machines, communicating across the network.  So stopping the
network interface should definitely break the connection.

Thanks

Phil


____________________Reply Separator____________________
Subject:    Re: [INTERFACES] libpq PQstatus problem
Author: "Joe Conway" <jconway2@home.com>
Date:       13/03/01 9:16 PM

>
> Then I stopped the network (eth0) on the postgreSQL server and hit
<return>
> again and still got
>
> > Connection status... OK
>
> as the output.  However Trying to execute the program with the postgreSQL
server
> offline resulted in the expected error messages, so it seems that in this
case
> the status was detected successfully.
>

I tried stopping the network on my machine, and was still able to connect
when logged on locally via psql. I presume this is because the local unix
sockets connection still works from the local machine. You might test this
by editing your pg_hba.conf file to disallow local sockets. e.g.:

local        all                                           reject


Hope this helps,

Joe