From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Subject: Feature request - have postgresql log warning  when new sub-release
	comes out.
Date: Wed, 25 Apr 2007 15:52:17 -0700
Organization: Hub.Org Networking Services
Lines: 26
Message-ID: <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
To: Carlos Moreno <moreno_pg@mochima.com>
User-Agent: Icedove 1.5.0.10 (X11/20070329)
In-Reply-To: <462E7317.2070707@mochima.com>
To: pgsql-general@postgresql.org

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?


(The thread started on the performance mailing lists but
I moved it to general since it drifted off topic).