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/