WA Pennant & Flag Displays - Darren wrote:
Thanks for your advice:
Do you get different messages with SSL disabled?
Yes - "Error connecting to the server: server closed the connection
unexpectedly. This probably means the server terminated abnormally before
or while processing the request."
Good - so it's not just SSL related.
Can you connect with psql locally?
No
Can you connect with psql via localhost?
No
Hmm - that makes the firewall options slightly less likely.
1. Make sure PG is listening on port 5432 and that log_connections is
set in your postgresql.conf. Then check your pg_hba.conf allows
connections from localhost and your local network. Restart PG.
2. Try telnetting to localhost, port 5432 (from the command-line in
Windows it should be "telnet localhost:5432" I think). If it connects,
hit return a couple of times and you should be disconnected.
PostgreSQL's logs should say something about an invalid startup packet.
If it doesn't even connect, then suspect a firewall.
The program installed was a web excelerator. I think the Windows Firewall
exceptions were turned off for PG and the program calling it. They are now
on.
Will try the ethereal option.
Seems less useful if you can't connect locally.
All recommended Windows updates are installed.
--
Richard Huxton
Archonet Ltd
---------------------------(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
