Weird startup behaviour

[N0L1M1T]

Hi,
I'm seeing some strange, and sadly fatal, startup behaviour with postgresql. That is, when the service starts it launches 4 windows service listeners but then proceeds to try to launch more. And apparently this causes the service startup to bail because the other 4 processes are attached to port 5432.

Try as I might I've not been able to fix this. Can somone help me out with this as the postgres service I have running on another equivalent XP box doesn't behave the same way.

Note: Firewalls are not an issue here.


Regards,
Dave

[kraada]

PostgreSQL normally uses a lot of processes. Each does a different thing and that's the reason why this database is as quick as it is. Four postgres processes aren't going to cause any problems.

Please report the problem you are experiencing though so that we can figure out what is causing it for you.

[N0L1M1T]

Yes, I know that there are 4 processes and that they're there for performance reasons. What I was saying is that the startup is starting 4 listeners and then trying to start 4 more which bail out cos the postgres port is unavailable. This in turn causes PT to abort cos it can't attach to the database.

[WhiteRider]

Please report your problem - you can attach the postgres logs too and that should give us an idea what is going on.