Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 649BD9FBA0B for ; Wed, 25 Apr 2007 23:52:55 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 68989-04 for ; Wed, 25 Apr 2007 23:52:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by postgresql.org (Postfix) with ESMTP id 1EE069FB9E3 for ; Wed, 25 Apr 2007 23:52:52 -0300 (ADT) Received: from working (c-71-60-105-193.hsd1.pa.comcast.net [71.60.105.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTP id 490BDEBC78; Wed, 25 Apr 2007 22:52:50 -0400 (EDT) Date: Wed, 25 Apr 2007 22:52:49 -0400 From: Bill Moran To: Ron Mayer Cc: Carlos Moreno , pgsql-general@postgresql.org Subject: Re: Feature request - have postgresql log warning when new sub-release comes out. Message-Id: <20070425225249.7ccdfa87.wmoran@potentialtech.com> In-Reply-To: <462FDBA1.4020800@cheapcomplexdevices.com> References: <75312DFA648AF74D8A236E5269BFBE4B04292F00@ncrx3.ncr.int.ec.gc.ca> <462E2537.2020706@archonet.com> <75312DFA648AF74D8A236E5269BFBE4B04292F02@ncrx3.ncr.int.ec.gc.ca> <6365.1177438176@sss.pgh.pa.us> <462E7317.2070707@mochima.com> <462FDBA1.4020800@cheapcomplexdevices.com> X-Mailer: Sylpheed version 2.2.10 (GTK+ 2.10.9; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/1105 X-Sequence-Number: 113008 Ron Mayer wrote: > > Carlos Moreno wrote: > > Tom Lane wrote: > >> Well, if you can't update major versions that's understandable; that's > >> why we're still maintaining the old branches. But there is no excuse > >> for not running a reasonably recent sub-release within your branch. > > > > Slammer..bug in Microsucks SQL Server....fix...had been available > > Feature request. > > How about if PostgreSQL periodically check for updates on the > internet and log WARNINGs as soon as it sees it's not running > the newest minor version for a branch. Ideally, it could > be set so the time-of-day's configurable to avoid setting off > pagers in the middle of the night. > > I might not lurk on the mailinglists enough to notice every > dot release; but I sure would notice if pagers went off with > warnings in the log files from production servers. > > Is that a possible TODO? If you switch to FreeBSD, you can easily have this done automatically with existing tools. ... Actually, I've a feeling that it would be trivial to do with just about any existing packaging system ... -- Bill Moran http://www.potentialtech.com