Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 24330632805 for ; Thu, 25 Mar 2010 13:01:51 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 30683-06 for ; Thu, 25 Mar 2010 16:01:40 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 9E49C632A29 for ; Thu, 25 Mar 2010 13:01:40 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o2PG1bSc019229; Thu, 25 Mar 2010 12:01:37 -0400 (EDT) To: "Steve Jones" Subject: Re: pg_stat: last vacuum and analyze times are not being updated - v8.3.5 cc: pgsql-admin@postgresql.org In-reply-to: <89B26B749E941749A0A5D173B4F86C3B0164BF25@MX01.jigsawhq.com> References: <89B26B749E941749A0A5D173B4F86C3B0164BD69@MX01.jigsawhq.com> <28922.1269359012@sss.pgh.pa.us> <89B26B749E941749A0A5D173B4F86C3B0164BE01@MX01.jigsawhq.com> <651.1269361151@sss.pgh.pa.us> <89B26B749E941749A0A5D173B4F86C3B0164BE05@MX01.jigsawhq.com> <825.1269361733@sss.pgh.pa.us> <89B26B749E941749A0A5D173B4F86C3B0164BE0C@MX01.jigsawhq.com> <1730.1269363770@sss.pgh.pa.us> <4438.1269370293@sss.pgh.pa.us> <89B26B749E941749A0A5D173B4F86C3B0164BE3D@MX01.jigsawhq.com> <20694.1269439886@sss.pgh.pa.us> <89B26B749E941749A0A5D173B4F86C3B0164BF25@MX01.jigsawhq.com> Comments: In-reply-to "Steve Jones" message dated "Thu, 25 Mar 2010 09:35:33 -0000" Date: Thu, 25 Mar 2010 12:01:37 -0400 Message-ID: <19228.1269532897@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/202 X-Sequence-Number: 34001 [ re-including the mailing list ] "Steve Jones" writes: > For your information, this is what I did last night. > Restarted the stats collector process, by issuing a kill -9 against it. > As you said, postgres started up a new collector process immediately. I > tried a few vacuums and the stats still weren't being updated. > I then restarted postgres in the hope this would help. It didn't. > I finally had to reboot the whole server which fixed the problem. As > you said, I have to run two manual vacuums before the stats are showing > up. This possible points a finger towards FreeBSD now? Would > appreciate your thoughts. If restarting Postgres didn't fix it then the problem has to have been at the operating system level. I can hardly think what the problem would have been exactly. It's not hard to imagine something going wrong in the kernel state for the UDP socket we use to send messages to the stats collector process; but restarting Postgres should have torn down that socket and created a new one. Perhaps something wrong in global state for all local UDP transfers? I dunno. But it seems like time to call in some FreeBSD hackers. regards, tom lane