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

From: "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Let's drop two obsolete features which are bear-traps for novices
Date: 2014-11-04 14:15:46
Message-ID: 20141104141546.GO32559@aart.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 04, 2014 at 11:44:22AM +0900, Michael Paquier wrote:
> On Sun, Nov 2, 2014 at 2:30 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > In the case of hash indexes, because we still have to have the hash
> > opclasses in core, there's no way that it could be pushed out as an
> > extension module even if we otherwise had full support for AMs as
> > extensions. So what I hear you proposing is "let's break this so
> > thoroughly that it *can't* be fixed". I'm not on board with that.
> > I think the WARNING will do just fine to discourage novices who are
> > not familiar with the state of the hash AM. In the meantime, we
> > could push forward with the idea of making hash indexes automatically
> > unlogged, so that recovering from a crash wouldn't be quite so messy/
> > dangerous.
> >
> There is as well another way: finally support WAL-logging for hash indexes.

+1

Ken

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2014-11-04 14:16:40 Re: Let's drop two obsolete features which are bear-traps for novices
Previous Message Andres Freund 2014-11-04 13:41:56 Re: Patch: add recovery_timeout option to control timeout of restore_command nonzero status code