| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Access method extendability |
| Date: | 2014-10-28 17:45:36 |
| Message-ID: | CA+U5nMLKdTuczcY=PukAJD9hbA9GbGs-ztH1WgVAi1KGXPBs=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 October 2014 17:06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> My own thought is that allowing external AMs is simply a natural
> consequence of PG's general approach to extensibility, and it would
> be surprising if we were to decide we didn't want to allow that.
If it wasn't clear from my two earlier attempts, yes, +1 to that.
I'd like to avoid all of the pain by making persistent AMs that are
recoverable after a crash, rather than during crash recovery.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-10-28 17:47:09 | Re: WIP: Access method extendability |
| Previous Message | Kirk Roybal | 2014-10-28 17:40:19 | lag_until_you_get_something() OVER () window function |