| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jeremy Haile <jhaile(at)fastmail(dot)fm>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Stats collector frozen? |
| Date: | 2007-01-26 09:23:05 |
| Message-ID: | 20070126092305.GB30416@svr2.hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 25, 2007 at 04:29:58PM -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Jeremy Haile wrote:
> >> If anyone else is experiencing similar problems, please post your
> >> situation.
>
> > All the Windows buildfarm machines are, apparently.
>
> Can't anyone with a debugger duplicate this and get a stack trace for
> us? If the stats collector is indeed freezing up, a stack trace showing
> where it's stuck would be exceedingly helpful.
Done some checking here. What happens is that suddenly the pgstats
socket stops receiving data. select() (pgstat.c line 1802) returns after
timeout, so got_data is always zero.
Interesting note: I just ran the serial regression tests, and they pass
fine. With the parallel tests, it always stops receiving data somewhere
during the first parallel group.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-01-26 09:46:11 | Re: Stats collector frozen? |
| Previous Message | Csaba Nagy | 2007-01-26 09:06:46 | Re: too many trigger records found for relation "item" - |