From: Ron Johnson <ron.l.johnson@cox.net>
To: pgsql-general@postgresql.org
Subject: Re: Re: Feature request - have postgresql log warning when new sub-release comes out.
Date: Thu, 26 Apr 2007 14:50:24 -0500
Message-ID: <46310280.2010301@cox.net> (raw)
In-Reply-To: <4630F1B4.2040806@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>
<462FE4F6.4020105@commandprompt.com>
<4630F1B4.2040806@cheapcomplexdevices.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/26/07 13:38, Ron Mayer wrote:
> Joshua D. Drake wrote:
>> Ron Mayer wrote:
>>> 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. ...
>> uhmmm gah, errm no... ehhhh why? :)
>
> Mostly because it seems like a near FAQ here that someone posts
> questions about people running very old postgresqls where the
> answers are "that was fixed in the latest minor version".
>
> Regarding people saying that their OS package manager can do this
> for them - I note that the people who have this problem the worst
> seem to be the people running older postgresqls, and your OS
> vendor may not be keeping the major version number of their
> postgresql the same as yours. For example, apt-cache search
> here isn't showing me 8.0 (though it does show 7.4, 8.1, and
> 8.2).
For example: Debian. It's Stable releases only get *security*
patches, nothing related to features or performance.
>> I could see a contrib module that was an agent that did that
>> but not as part of actual core.
>
> I was thinking it would protect the more ignorant users who
> didn't even know about contrib. I imagine anyone who did know
> enough to install a contrib module would also know how to write
> such a script without it.
>
> No big deal, though - if others don't think there's a need, then
> I'm not going to push for it.
A *tiny* Perl/Python script to parse
http://www.postgresql.org/versions.xml is all you need. Putting it
in cron and emailing when "someone" a version changes seems useful.
Ok, it's official: you're elected to implement it!
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGMQJ/S9HxQb37XmcRAgUEAKDWKzM8scO7Mc8uB26iqIo8WnJGmwCg6e4w
vRuaSXH0sMhtnNZbYsuDKmc=
=wGYf
-----END PGP SIGNATURE-----
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ron.l.johnson@cox.net, pgsql-general@postgresql.org
Subject: Re: Re: Feature request - have postgresql log warning when new sub-release comes out.
In-Reply-To: <46310280.2010301@cox.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox