Tom Lane wrote:
> Don Y <pgsql@DakotaCom.Net> writes:
>> Jim C. Nasby wrote:
>>> This is a very minor reason why you should be running the most recent
>>> 8.0.x release and not 8.0.3. A much bigger reason is that there are
>>> data-loss bugs that have been fixed.
>
>> The folks watching the Postgres releases haven't yet said
>> we need to "step forward".
>
> Are these folks actually watching, or just asleep at the wheel?
>
> 8.0.4, 8.0.5, and 8.0.6 each contain a fix for a can-bite-anyone-at-
> any-time data-loss bug. Even if you are convinced you do not care
> about any of the numerous other bugs those releases fix, I will have
> zero sympathy for you when your 8.0.3 installation eats your data
> because of one of those bugs.
>
>> I don't believe any other folks have experienced major lossage
>> (here) under 8.0.3.
>
> Read the archives. Other people have gotten bit; are you feeling
> lucky? If so why?
>
> (Just for the record, there are new updates coming out Tuesday,
> and my actual recommendation today would be to wait for 8.0.8.
> But once it's out, you need to get off your duff.)
We aren't populating tables. Most of our work is involved
in the things *around* the database (the database is just a
small piece of the puzzle). I, for example, drop all of
my tables at the end of each work day -- along with most
of the extensions I have loaded... things on the "outside"
are just changing far more than the database itself.
I'm sure once the framework *around* the database is
stable and resilient enough, then the database will look
like it needs attention -- and the order will come out
to upgrade (to which version, I don't know... "it's not
my job" :> )