Re: Backend died while dropping index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mike Mascari <mascarm(at)mascari(dot)com>
Cc: brianb-pggeneral(at)edsamail(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: Backend died while dropping index
Date: 2000-06-18 05:12:30
Message-ID: 11302.961305150@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Mike Mascari <mascarm(at)mascari(dot)com> writes:
> brianb-pggeneral(at)edsamail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2000-06-18 14:16:50 Re: Installing clients (psql) only
Previous Message K Parker 2000-06-18 05:08:04 record-locking protocol for interactive users