From: Andrew Sullivan <ajs@commandprompt.com>
To: pgsql-admin@postgresql.org
Subject: Re: Bug introduced in 8.0
Date: Wed, 27 Aug 2008 12:58:12 -0400
Message-ID: <20080827165811.GG18946@commandprompt.com> (raw)
In-Reply-To: <QoSdnab0w_t0PinVnZ2dnUVZ_sCdnZ2d@comcast.com>
References: <15aa6b3e0808260421r1b97b7dfoa53fd6f04ffbd49b@mail.gmail.com>
<20080826131023.GJ10936@commandprompt.com>
<dcc563d10808260749rba42897sba206f471428b1a2@mail.gmail.com>
<QoSdnab0w_t0PinVnZ2dnUVZ_sCdnZ2d@comcast.com>
On Tue, Aug 26, 2008 at 08:46:33PM -0400, Lew wrote:
> upgrades to PG, it is our duty to inform our bosses of the risk of not
> upgrading, so they can properly assess risks and manage them accordingly.
I agree. It is, by the same token, your duty to yourself to ensure
that, if the answer is, "No," you get that answer in writing so that
future failures are not possibly pinned on you as having been
negligent in installing stability and security releases.
By the way, I always refer to these of late as "security and
stability" rather than "minor" releases. I do that because it
presents them to the target audience in a way that is understandable.
Those releases are, for the project, a maintenance burden and not a
way to introduce features. It's wise to keep that in mind when
presenting such releases to managers responsible for the decision.
A
--
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
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-admin@postgresql.org
Cc: ajs@commandprompt.com
Subject: Re: Bug introduced in 8.0
In-Reply-To: <20080827165811.GG18946@commandprompt.com>
* 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