From: | "Thomas T(dot) Thai" <tom(at)minnesota(dot)com> |
---|---|
To: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: stale portmaster processes |
Date: | 2001-01-14 20:56:21 |
Message-ID: | Pine.NEB.4.21.0101141455180.889-100000@ns01.minnesota.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, 13 Jan 2001, Thomas T. Thai wrote:
> Date: Sat, 13 Jan 2001 01:12:29 -0600 (CST)
> From: Thomas T. Thai <tom(at)minnesota(dot)com>
> To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
> Subject: stale portmaster processes
>
> i've noticed that when using php scripts or the "c" cgi search.cgi from
> mnogosearch, if i access either script from the web browser and stop it
> with ESC in the middle of it trying to access the pgsql db, the associated
> postmaster process hangs around forever and won't disappear:
>
> 19276 p1 I 0:00.11 postmaster: web mnwork [local] idle (postgres)
> 19920 p1 I 0:00.08 postmaster: web mnwork [local] idle (postgres)
> 19958 p1 I 0:00.10 postmaster: web mnwork [local] idle (postgres)
>
> i hope this isn't normal.
i've not yet seen any stale idling postmaster processes with the latest
cvs source. the above was from mid december cvs source where i saw the
stale postmasters (with --enable-debug).
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-14 20:57:36 | Re: performance hit with --enable-debug |
Previous Message | Thomas T. Thai | 2001-01-14 20:53:46 | Re: Re: performance hit with --enable-debug |