From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ameet Kini <akini(at)cs(dot)wisc(dot)edu> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Lots of postmaster processes |
Date: | 2005-12-13 19:10:11 |
Message-ID: | 9263.1134501011@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ameet Kini <akini(at)cs(dot)wisc(dot)edu> writes:
> We're running on tao linux. And yes, there are many client connection
> requests sent to the server at the same time. My impression was that
> client connection requests usually show up as a postgres process not
> postmaster but I could be wrong. Is it that the postmaster forks off a
> process on receiving a client connection request and then renames the
> process to postgres and I'm issuing my ps command while its in the
> intermediate state when its still called postmaster?
A bit hard to believe, unless there's something delaying the
subprocesses from reaching their first set_ps_display() call.
Offhand it looks like DNS problems could cause that (especially if
you've got log_hostname enabled), or broken client code that doesn't
send the whole startup packet immediately.
However, a backend that's hung up that early in the startup process
really shouldn't be consuming noticeable resources, so I'm not sure why
this would create a performance issue for you.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Diego | 2005-12-13 20:12:20 | Driver JDBC... |
Previous Message | Chris Hoover | 2005-12-13 18:59:30 | Re: PG 8.1.1 rhel-as-4 rpms missing - Now not initdb issues |