| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Access method extendability |
| Date: | 2014-10-28 20:25:27 |
| Message-ID: | CA+U5nMLR4WZq-tvNKxLKdZd+Qo0QtR_hQfHokt53F=N_kwjQ3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 October 2014 17:58, Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> Also, I'm not sure that many users have enough of courage to use unlogged
> AMs. Absence of durability is only half of trouble, another half is lack of
> streaming replication. I think if we have unlogged GIN then external
> indexing engines would be used by majority of users instead of GIN.
Please answer the problem I have raised.
How will you act when the new AM that you write breaks?
How will you advise your users that the durability they sensibly
desire is actually causing them data loss?
I haven't opposed your ideas in this patch; I have only observed the
necessary surrounding infrastructure is incomplete.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-10-28 20:27:21 | Re: WIP: Access method extendability |
| Previous Message | Simon Riggs | 2014-10-28 20:17:57 | Re: WIP: Access method extendability |