Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id A013D9FBA5A for ; Wed, 25 Apr 2007 20:32:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 79156-09 for ; Wed, 25 Apr 2007 20:31:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 46C8B9FB9C8 for ; Wed, 25 Apr 2007 20:31:58 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l3PNVJRp016519; Wed, 25 Apr 2007 16:31:20 -0700 Message-ID: <462FE4F6.4020105@commandprompt.com> Date: Wed, 25 Apr 2007 16:32:06 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: Ron Mayer CC: Carlos Moreno , pgsql-general@postgresql.org Subject: Re: Feature request - have postgresql log warning when new sub-release comes out. 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> In-Reply-To: <462FDBA1.4020800@cheapcomplexdevices.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 25 Apr 2007 16:31:21 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/1099 X-Sequence-Number: 113002 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. uhmmm gah, errm no... ehhhh why? :) I could see a contrib module that was an agent that did that but not as part of actual core. Joshua D. Drake > > 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? > > > > (The thread started on the performance mailing lists but > I moved it to general since it drifted off topic). > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/