Skip site navigation (1) Skip section navigation (2)

Re: Postmaster process on port 10000

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Volker Aßmann <volker(at)twisted-nerve(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Postmaster process on port 10000
Date: 2006-04-28 15:45:14
Message-ID: 1413.1146239114@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Volker =?ISO-8859-1?Q?A=DFmann?= <volker(at)twisted-nerve(dot)de> 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

In response to

pgsql-general by date

Next:From: Chris BrowneDate: 2006-04-28 15:55:27
Subject: Re: Alternative for vacuuming queue-like tables
Previous:From: Csaba NagyDate: 2006-04-28 15:33:58
Subject: Re: Alternative for vacuuming queue-like tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group