Skip site navigation (1) Skip section navigation (2)

Re: Hung postmaster (8.3.9)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Hung postmaster (8.3.9)
Date: 2010-03-01 23:49:31
Message-ID: 27134.1267487371@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
"Ed L." <pgsql(at)bluepolka(dot)net> writes:
> Also seeing lots of postmaster zombies (190 and growing)...

Yeah, that and the lack of service for new connections would both be
expected if the postmaster is stuck.  And the autovac worker start
failures, too.  There's only one bug here.

> While new connections are hanging, top shows postmaster using 
> 100% of cpu.

Oh, for some reason I thought it was sitting idle.  That sounds more
like an infinite loop.  Try reattaching to the postmaster, confirm the
stack trace, and then see how many times you can do "fin" before it
doesn't return control.  That will tell us which level of subroutine is
looping.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-03-01 23:57:24
Subject: Re: Hung postmaster (8.3.9)
Previous:From: Merlin MoncureDate: 2010-03-01 23:42:53
Subject: Re: scheduler in core

pgsql-general by date

Next:From: Tom LaneDate: 2010-03-01 23:57:24
Subject: Re: Hung postmaster (8.3.9)
Previous:From: Ed L.Date: 2010-03-01 23:40:55
Subject: Re: Hung postmaster (8.3.9)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group