Re: Let's drop two obsolete features which are bear-traps for novices - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Let's drop two obsolete features which are bear-traps for novices
Date
Msg-id 8275.1414867700@sss.pgh.pa.us
Whole thread Raw
In response to Re: Let's drop two obsolete features which are bear-traps for novices  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Let's drop two obsolete features which are bear-traps for novices  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-11-01 14:39:21 -0400, Tom Lane wrote:
>> What exactly do you think is going to make a crashed unlogged index valid
>> again without a REINDEX?  Certainly the people who are currently using
>> hash indexes in the way Andrew describes are expecting to have to REINDEX
>> them after a crash.

> Obviously that individual index needs to be recreated. What I mean is
> that I don't think it'll be acceptable that the table essentially can't
> be queried before that's done. The situations in which I'd found
> unlogged indexes useful is where there's some indexes are critical for
> the OLTP business (those would continue to be logged), but some other
> large ones are for things that aren't absolutely essential. Reports and
> such.

Sure.  And as long as you aren't issuing queries that would want to scan
the crashed index, it won't matter either way.  The question is whether
you'd rather that your "inessential reporting queries" fail without the
broken index, or that they take extreme amounts of time/resources.
I don't think it's obvious that the first alternative is bad.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Let's drop two obsolete features which are bear-traps for novices
Next
From: Andres Freund
Date:
Subject: Re: Let's drop two obsolete features which are bear-traps for novices