| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Justin <justin(at)emproshunts(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: postgre vs MySQL |
| Date: | 2008-03-12 03:11:32 |
| Message-ID: | dcc563d10803112011w7d4b554bx32ecc433bd84809a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 11, 2008 at 7:33 PM, Justin <justin(at)emproshunts(dot)com> wrote:
>
>
> I view updates/patches of any kind like this, if ain't broke don't fix it.
> I normally only update computers with security patches only after i prove it
> don't destroy installs.
But that's juast it. When a postgresql update comes out, it is
precisely because the database IS broken. A bug that might eat your
data or allow an attacker to get into your database are the kinds of
fixes, and the only kind really, that go into production pgsql
releases. I too wait a day or two to test it on a staging server, but
I've never had a pgsql update blow back in my face, and I've done an
awful lot of them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin | 2008-03-12 05:09:25 | Re: postgre vs MySQL |
| Previous Message | Justin | 2008-03-12 02:33:14 | Re: postgre vs MySQL |