The following bug has been logged online:

Bug reference: 1445
Logged by: John Anson
Email address: postgres (AT) jomich (DOT) com
PostgreSQL version: 8.0.0.5017
Operating system: Windows XP SP2
Description: Installation failed during "Activating Procedural
Languages" - "Failed to connect to the database"
Details:

(I'm new to PostgreSQL)
I'm trying to install PostgreSQL v8.0.0.5017 (from postgresql-8.0.msi) on
Windows XP SP2.
The installation pauses with a dialog box message "PostgreSQL 8.0: Failed to
connect to the database. Procedural languages are installed, but not
activated in any databases", then "PostgreSQL 8.0: server closed the
connection unexpectedly. This problem means the server terminated abnormally
before or while processing the request", then "PostgreSQL 8.0: Failed to
connect to the database. Contrib files are installed, but are not activated
in any databases.", then a repeat of the 2nd dialog.

When I run pgAdmin III, I cannot connect to the database server, and get the
same error message: "server closed the connection unexpectedly ...".
I have listed the contents of the database log file below.

Before the installation I:
- shut down ZoneAlarm Security Suite (firewall and virus protection)
- disabled Windows Firewall
- exited all applications and SystemTray icons.
- terminated non-Microsoft processes

I tried the Postgres installation on the same hardware with a fresh copy of
Windows XP SP2, and the installation worked without any problem.

However, I would like to not have to reinstall my workstation to get
Postgres installed.
The fault I am having seems similar to the LSP bug that I saw mentioned in
some of the 8.0 release candidates.
I saw messages about a tool to fix LSP problems.
However, I could not find the tool.

....

By chance, I stumbled across the LSPfix tool while I was preparing this bug
report.
After I ran the tool, I could connect to the database from pgAdmin.

My issues now are:
1. Should the Postgres windows .msi installation require the LSPfix tool?
(It did in my case).
2. It would have saved me a lot of grief if the tool was mentioned in the
instalation FAQ (as some posts referred to, but the FAQ must have been
changed). Should the tool be mentioned in the FAQ?

If it would help, I can restore my workstation to the state it was in when
the installation was failing to test any fixes you might develop.







Database log file (D:\Program
Files\PostgreSQL\8.0\data\pg_log\postgresql-2005-01-28_172246.log) are:

2005-01-28 17:22:46 LOG: database system was shut down at 2005-01-28
17:22:42 New Zealand Standard Time
2005-01-28 17:22:46 LOG: checkpoint record is at 0/AC3330
2005-01-28 17:22:46 LOG: redo record is at 0/AC3330; undo record is at 0/0;
shutdown TRUE
2005-01-28 17:22:46 LOG: next transaction ID: 546; next OID: 17230
2005-01-28 17:22:46 LOG: database system is ready
2005-01-28 17:22:48 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:48 LOG: incomplete startup packet
2005-01-28 17:22:49 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:49 LOG: incomplete startup packet
2005-01-28 17:22:50 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:50 LOG: incomplete startup packet
2005-01-28 17:22:51 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:51 LOG: incomplete startup packet
2005-01-28 17:22:52 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:52 LOG: incomplete startup packet
2005-01-28 17:22:53 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:53 LOG: incomplete startup packet
2005-01-28 17:22:55 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:55 LOG: incomplete startup packet
2005-01-28 17:22:56 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:56 LOG: incomplete startup packet
2005-01-28 17:22:57 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:22:57 LOG: incomplete startup packet
2005-01-28 17:22:58 LOG: could not receive data from client: No connection
could be made because the target machine actively refused it.
2005-01-28 17:22:58 LOG: incomplete startup packet
2005-01-28 17:23:09 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:09 LOG: incomplete startup packet
2005-01-28 17:23:10 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:10 LOG: incomplete startup packet
2005-01-28 17:23:12 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:12 LOG: incomplete startup packet
2005-01-28 17:23:13 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:13 LOG: incomplete startup packet
2005-01-28 17:23:14 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:14 LOG: incomplete startup packet
2005-01-28 17:23:15 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:15 LOG: incomplete startup packet
2005-01-28 17:23:16 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:16 LOG: incomplete startup packet
2005-01-28 17:23:17 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:17 LOG: incomplete startup packet
2005-01-28 17:23:19 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:19 LOG: incomplete startup packet
2005-01-28 17:23:20 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:23:20 LOG: incomplete startup packet
2005-01-28 17:25:01 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:25:01 LOG: incomplete startup packet
2005-01-28 17:25:02 LOG: could not receive data from client: An operation
was attempted on something that is not a socket.
2005-01-28 17:25:02 LOG: incomplete startup packet

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

<snip>

No, it shouldn't. Which LSP was it that was causing the problem? And can
you identify which software it came with.


Yes. It was there during RC, but it was beleived that we had a
workaround in place that would not cause the problem to happen again. It
looks like it's going to have to back.


//Magnus

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org