This is a discussion on Re: Socket problem using beta2 on Windows-XP within the pgsql Hackers forums, part of the PostgreSQL category; --> > >IIRC, the win32 installer will enable autovacuum by default. > And yes, > >autovacuum was my first thought ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| > >IIRC, the win32 installer will enable autovacuum by default. > And yes, > >autovacuum was my first thought as well after Thomas last > mail - that > >would be a good explanation to why it happens when the postmaster is > >idle. > > > > > I used the win32 installer defaults so autovacuum is > probably a safe assumption. Right. Please try turning it off and see if the problem goes away. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| |||
| Magnus Hagander wrote: >Right. Please try turning it off and see if the problem goes away. > > It does (go away). - thomas ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| |||
| Magnus Hagander wrote: >Right. Please try turning it off and see if the problem goes away. > > No, wait! It does *not* go away. Do I need to do anything more than setting this in my postgresql.conf file: autovacuum = false # enable autovacuum subprocess? and restart the service? The two zombie entries occurs directly when I start the service, then there's two new entries popping up every minute. - thomas ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| |||
| On Fri, Sep 30, 2005 at 08:29:07AM +0200, Thomas Hallgren wrote: > Magnus Hagander wrote: > > >Right. Please try turning it off and see if the problem goes away. > > > > > No, wait! It does *not* go away. Do I need to do anything more than > setting this in my postgresql.conf file: > > autovacuum = false # enable autovacuum subprocess? > > and restart the service? > > The two zombie entries occurs directly when I start the service, then > there's two new entries popping up every minute. If it's two zombies per minute, then I bet it's the stat collector and stat bufferer. They are restarted by the postmaster if not found to be running. The weird thing is that the postmaster _should_ call wait() for them if it detects that they died (when receiving a SIGCHLD signal AFAIR). If it doesn't, maybe it indicates there's a problem with the signal handling on Win32. -- Alvaro Herrera Valdivia, Chile ICBM: S 39º 49' 17.7", W 73º 14' 26.8" "We are who we choose to be", sang the goldfinch when the sun is high (Sandman) ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |
| |||
| Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > If it's two zombies per minute, then I bet it's the stat collector and > stat bufferer. They are restarted by the postmaster if not found to be > running. That would make some sense, because the stat processes need to set up new sockets (for the pipe between them). The autovacuum theory didn't hold any water in my eyes because autovacuum doesn't create any new sockets. However, why two zombies? That would mean that the grandchild process started, which should mean that the pipe was already created ... Does Windows have any equivalent of strace whereby we could watch what's happening during stats process launch? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| ||||
| Tom Lane wrote: >However, why two zombies? That would mean that the grandchild process >started, which should mean that the pipe was already created ... > > To clarify, I talk about the tcpview window and connections, and thus zombi-connections. They both belong to the same pid and seems to point to eachother. The actual process no longer exists (it can't be viewed anywhere). Regards, Thomas Hallgren ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |