Re: Stats collector frozen?

From: "Jeremy Haile" <jhaile(at)fastmail(dot)fm>
To: "Magnus Hagander" <magnus(at)hagander(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Stats collector frozen?
Date: 2007-01-26 15:07:31
Message-ID: 1169824051.30848.1171376725@webmail.messagingengine.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> We have had lots of reports of issues with the stats collector on
> Windows. Some were definitly fixed by the patch by O&T, but I don't
> think all.

Here were a couple of other reports I found:
http://archives.postgresql.org/pgsql-hackers/2006-09/msg00415.php
http://archives.postgresql.org/pgsql-hackers/2006-04/msg00127.php

> The thing is, since it didn't give any error messages at all, most users
> wouldn't notice. Other than their tables getting bloated, in which case
> they would do a manual vacuum and conlcude autovacuum wasn't good
> enough. Or something.

This is indeed what I assumed at first. I started running "vacuum
analyze" hourly and turned off autovacuum. Later, I decided to try the
autovacuum route again and investigated why it wasn't working well.

Magnus - could you send me a patched exe to try in my environment?
Would it be compatible with 8.2.1?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-01-26 15:12:00 Re: "no unpinned buffers available" ? why? (hstore and plperl involved)
Previous Message Magnus Hagander 2007-01-26 15:01:22 Re: Stats collector frozen?