I respectfully disagree Tom, for various reasons:
1) Postgres 6.5.3 is a known quantity, and there are more people familiar
with
the common, critical problems, so there are more people who can help solve
problems.
2) 7.0.2 undoubtedly has some new bugs and problems that are not
apparent yet - bugs that could sink a commercial business that depends
on Postgres (like mine)
3) In some cases (perhaps not 6.5.3, but some), the entire database must be
dumped and restored, which is difficult for a commercial business to
"just do it".
4) Various 3rd party applications and various exotic queries need to be
verified against the new platform.
5) A variety of the common existing queries need to be re-evaluated and
compared
in terms of speed, since there have been several reports of 'slowness' in
queries.
I'm sure you're frustrated by us laggards. But frankly, my entire business
depends on
Postgres, and I'm not going to risk it just because there's an upgrade that
may or
may not fix some of my problems, and will undoubtedly create new ones. If
you can
get the guys from Great Bridge to send out general announcements that they
have
tested it, and are satisfied that it will work properly, then I will
consider upgrading
sooner.
jb
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Mike Mascari" <mascarm@mascari.com>
Cc: <brianb-pggeneral@edsamail.com>; <pgsql-general@postgresql.org>
Sent: Sunday, June 18, 2000 1:12 AM
Subject: Re: [GENERAL] Backend died while dropping index
> Mike Mascari <mascarm@mascari.com> writes:
> > brianb-pggeneral@edsamail.com wrote:
> >> How do I fix this? This is on 6.5.
>
> > 1. Change to the location of the datafiles, which, for a
> > database, called "mydatabase" will look something like:
> > 2. Create an empty file of the name of the index:
> > 3. Delete the file using psql:
> > 4. Recreate the index as appropriate
>
> And
>
> 5. Update to 7.0.2 at your earliest convenience, if not sooner.
>
> No smileys here. I've noticed several people lately saying they're
> still on 6.5 (or earlier :-() because they're "waiting for 7.0 to
> settle out". Wake up and smell the roses folks. 7.0 certainly has
> bugs, and maybe a few teething pains yet to go, but it has far fewer
> bugs than any prior release --- and most of the bugs it does have
> are undoubtedly present in prior releases as well. Holding off on
> an update isn't buying you anything except continued exposure to the
> hundreds of bugs we've swatted since 6.5.
>
> regards, tom lane
