Volker =?ISO-8859-1?Q?A=DFmann?= <volker@xxxxxxxxxxxxxxxx> writes: > We have a problem with our postmaster process, which normaly runs on port > 5432. From time to time it spawns another process which listens on port > 10000 - which also happens to be the port for our own server. I don't find > any configuration option which could cause this behaviour. [ excuse me while I retrieve my eyebrows from the back side of my head ] There isn't anything in the PG code that would do that. Have you got any modified code in there? It might be educational to attach to the port-10000-using process with a debugger and get a stack trace from it. regards, tom lane
