From: Scott Marlowe <scott.marlowe@gmail.com>
To: Andrew Sullivan <ajs@commandprompt.com>
To: pgsql-admin@postgresql.org
Subject: Re: Bug introduced in 8.0
Date: Wed, 27 Aug 2008 11:05:53 -0600
Message-ID: <dcc563d10808271005heae032arc85cc0559dd5644c@mail.gmail.com> (raw)
In-Reply-To: <20080827165811.GG18946@commandprompt.com>
References: <15aa6b3e0808260421r1b97b7dfoa53fd6f04ffbd49b@mail.gmail.com>
<20080826131023.GJ10936@commandprompt.com>
<dcc563d10808260749rba42897sba206f471428b1a2@mail.gmail.com>
<QoSdnab0w_t0PinVnZ2dnUVZ_sCdnZ2d@comcast.com>
<20080827165811.GG18946@commandprompt.com>
On Wed, Aug 27, 2008 at 10:58 AM, Andrew Sullivan <ajs@commandprompt.com> wrote:
> 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.
I used to work for an Oracle DBA and while he was quite smart in most
ways, he really had been trained by Oracle to avoid anything but
"patches". Upgrades / updates of a db were very scary for him. I had
to present the minor updates as "patch releases" to get him
comfortable with them. And have a full implementation plan and all
that as well.
But if instead he had insisted on running an outdated version of
PostgreSQL for some goofy reason I would have been looking for another
job.
I guess I've been lucky in that I've never actually had to work for
idiots. Sure have interviewed with quite a few though.
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: scott.marlowe@gmail.com, ajs@commandprompt.com
Subject: Re: Bug introduced in 8.0
In-Reply-To: <dcc563d10808271005heae032arc85cc0559dd5644c@mail.gmail.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