| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-01 18:15:29 |
| Message-ID: | 20141101181529.GI17790@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-11-01 14:13:02 -0400, Andrew Dunstan wrote:
> Yes, although there might not be much reason to use them either. I think
> Tom's first step of making hash indexes automatically unlogged makes sense.
> Longer term I'd like to see unlogged as an option for all AMs - especially
> btree.
If we implement unlogged indexes, it should definitely work for all
builtin indexes.
> It makes plenty of sense to me to be able to make the data resilient
> even if the indexes, which can after all be recreated in the unlikely event
> of a crash, are not.
While I agree that it can be useful, I think the fact that replicas/HS
can't use such index makes them far less useful.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-11-01 18:19:22 | Re: Let's drop two obsolete features which are bear-traps for novices |
| Previous Message | Andrew Dunstan | 2014-11-01 18:13:02 | Re: Let's drop two obsolete features which are bear-traps for novices |