I ran process explorer and looked at the handles for the System process. The vast majority of the handles are of type "Key". I can find them in the registry. I took two at random from process explorer and exported the registry branch for them below.
## EXAMPLE 1: ##
Key Name: HKEY_CLASSES_ROOT\CLSID\{9F074EE2-E6E9-4d8a-A047-EB5B5C3C55DA}
Class Name: <NO CLASS>
Last Write Time: 2/28/2012 - 1:26 AM
Value 0
Name: <NO NAME>
Type: REG_SZ
Data: HwTextInsertion Class
Key Name: HKEY_CLASSES_ROOT\CLSID\{9F074EE2-E6E9-4d8a-A047-EB5B5C3C55DA}\InprocServer32
Class Name: <NO CLASS>
Last Write Time: 2/29/2012 - 4:05 AM
Value 0
Name: <NO NAME>
Type: REG_EXPAND_SZ
Data: %CommonProgramFiles%\microsoft shared\ink\tiptsf.dll
Value 1
Name: ThreadingModel
Type: REG_SZ
Data: Apartment
Key Name: HKEY_CLASSES_ROOT\CLSID\{9F074EE2-E6E9-4d8a-A047-EB5B5C3C55DA}\ProgID
Class Name: <NO CLASS>
Last Write Time: 2/29/2012 - 4:05 AM
Key Name: HKEY_CLASSES_ROOT\CLSID\{9F074EE2-E6E9-4d8a-A047-EB5B5C3C55DA}\Server
Class Name: <NO CLASS>
Last Write Time: 2/29/2012 - 4:05 AM
## EXAMPLE 2: ##
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80FF6842-51A9-4959-B3B9-EE4DCBFD7740}
Class Name: <NO CLASS>
Last Write Time: 2/28/2012 - 12:07 AM
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80FF6842-51A9-4959-B3B9-EE4DCBFD7740}\Programmable
Class Name: <NO CLASS>
Last Write Time: 12/13/2010 - 12:27 PM
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80FF6842-51A9-4959-B3B9-EE4DCBFD7740}\InprocServer32
Class Name: <NO CLASS>
Last Write Time: 2/29/2012 - 3:05 AM
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80FF6842-51A9-4959-B3B9-EE4DCBFD7740}\ProgID
Class Name: <NO CLASS>
Last Write Time: 2/29/2012 - 3:05 AM
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{80FF6842-51A9-4959-B3B9-EE4DCBFD7740}\Server
Class Name: <NO CLASS>
Last Write Time: 2/29/2012 - 3:05 AM
## END EXAMPLES ##
A common thread I notice when looking through the keys is InprocServer32.
Adam Bruss
Senior Development Engineer
AWR Corporation
11520 N. Port Washington Rd., Suite 201
Mequon, WI 53092 USA
P: 1.262.240.0291 x104
F: 1.262.240.0294
E: abruss@xxxxxxxxxxx
W: http://www.awrcorp.com
-----Original Message-----
From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of dennis jenkins
Sent: Tuesday, February 28, 2012 4:01 PM
To: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: accumulating handles problem on machine running postgresql
On Tue, Feb 28, 2012 at 8:48 AM, Adam Bruss <abruss@xxxxxxxxxxx> wrote:
> The handles persist through restarting the postgresql service and restarting the IIS server. The handles are accumulating on the System process. I think the handles are created when the web service is accessed but that would mean the IIS worker processes would have responsibility and they don't seem to. Recycling the worker processes in IIS does nothing. And the worker processes have their own process w3wp.exe which never accumulate handles. It's probably not a postgresql thing or other people would be seeing it.
>
Use "process explorer" from sysinternals / microsoft (google for it)
to see what these handles are for (pipes, files, events, mutants,
desktops, winstations (ok, probably not those), etc...
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
