dbTalk Databases Forums  

[BUGS] Infinite increment of postgre.exe in taskmanager

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss [BUGS] Infinite increment of postgre.exe in taskmanager in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
AT
 
Posts: n/a

Default [BUGS] Infinite increment of postgre.exe in taskmanager - 06-02-2006 , 01:30 AM






Hi

Newbie when it comes down to postgre.

OS: Windows XP SP2 Pro Dutch

When I run a DMS (Xinco) that uses postgre (I only use postgre for this), a
service is started. Xinco uses a separate limited Xinco User account.

After starting the service I see several postgre.exe services running of
various sizes. That's fine.

After an hour or so I see several postgre.exe services running (up to 200
and still increasing) and it is the postgre.exe 76kb that is in that huge
number (even when nobody uses Xinco, it still continous).

When I stop the PostgreSQL service then the large kb postgre.exe disappears
from the task manager ...but all those 76kb postgre.exe remain in memory.

Any ideas?

Stefan


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Reply With Quote
  #2  
Old   
AT
 
Posts: n/a

Default Re: [BUGS] Infinite increment of postgre.exe in taskmanager - 06-02-2006 , 03:50 AM






Quote:
Hi
=20
Newbie when it comes down to postgre.
=20
OS: Windows XP SP2 Pro Dutch
=20
When I run a DMS (Xinco) that uses postgre (I only use=20
postgre for this), a service is started. Xinco uses a=20
separate limited Xinco User account.
=20
After starting the service I see several postgre.exe services=20
running of various sizes. That's fine.
=20
After an hour or so I see several postgre.exe services=20
running (up to 200 and still increasing) and it is the=20
postgre.exe 76kb that is in that huge number (even when=20
nobody uses Xinco, it still continous).
=20
When I stop the PostgreSQL service then the large kb=20
postgre.exe disappears from the task manager ...but all those=20
76kb postgre.exe remain in memory.
=20
Any ideas?
If you actually have postgre.exe files there, you need to talk to
whomever yuo got that from, because that's not PostgreSQL.

If you have postgres.exe files, which is the PostgreSQL backend exe,
then you need to check your logs (both eventlog and the pg_log
directory, depending on how it's configured) for error messagesn that
will indicate what yourp roblem is.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly


Reply With Quote
  #3  
Old   
AT
 
Posts: n/a

Default Re: [BUGS] Infinite increment of postgre.exe in taskmanager - 06-02-2006 , 12:27 PM



[list re-added]

Quote:
In the eventlog I found quite often the following (therefore=20
I assume it has to do with those many postgres.exe's). Does=20
this give an indication where to look for the problem/solution?
Yes, it definitly does.


Quote:
gegevens zijn deel van de gebeurtenis: LOG: unexpected EOF=20
on client connection (Can't find description of event-ID (0)=20
in the source (PosgreSQL) The local computer might not have=20
the necessary registry data or DLL-message files to display=20
messages from an external computer. You might want to try=20
the option /AUXsource=3D to obtain these descriptions, see Help=20
and support for more details. The following data are part of=20
the event: LOG: unexpected EOF on the client connection)
First - the fact that it can't find the DLL message file shows that
PostgreSQL is not properly installed. I take it it wasn't installed
using the official installer?

The "unepxected EOF" message is normal for any client that exits without
explicitly closing the connection.

Quote:
support for more details. The following data are part of the=20
event: FATAL: could not duplicate socket 1772 for use in the=20
backend: error code 10038)
This is a not too uncommon error, meaning that something broke your
TCP/IP stack. We've seen this many times, and it's usually either
antivirus or personal firewall software. If you have any of those on the
machine, try uninstalling them and see if that helps (sometimes it's
enough to disable them for the pg processes, sometimes you need to
uninstall them completely).

If that doesn't help, search for LSPfix - it's a tool that can help you
fix it.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.