From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Andy Shellam <andy-lists(at)networkmail(dot)eu>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Yum upgrade of PostgreSQL 8.4 from to rc1 rendered data unusable |
Date: | 2009-06-16 17:17:26 |
Message-ID: | dcc563d10906161017l67a54ccel4ad94f29559952ee@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
2009/6/16 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= <devrim(at)gunduz(dot)org> writes:
>> Anyway, we are talking about an issue which should never ever happen, if
>> docs were read. I announced -devel RPMs lots of times, and each one
>> included a notice for dump/reload action.
>
> I think the real issue here is that the OP was confused about whether
> the devel RPMs represented a playpen or something that could be used for
> production data. It's hard to say whether we didn't convey that message
> clearly enough, or he failed to pay enough attention, but probably some
> blame can be assigned on both sides of that.
This whole thread should serve as a lesson in change control /
management to a server. If you aren't paying attention to the
upgrades / updates of your production servers you're asking for
trouble.
From | Date | Subject | |
---|---|---|---|
Next Message | Tena Sakai | 2009-06-16 18:07:27 | an incident maybe worth reporting |
Previous Message | Tom Lane | 2009-06-16 17:07:03 | Re: Yum upgrade of PostgreSQL 8.4 from to rc1 rendered data unusable |