| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Advocacy Group <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Let's start talking features and "theme" for 9.4 |
| Date: | 2014-04-23 20:06:26 |
| Message-ID: | CA+U5nMLsTCmQSmeLaMwMr+Dv_9Fu-+DG0-sojmuY8UxGrct8Xg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 23 April 2014 20:55, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Simon Riggs wrote:
>
>> Logical Decoding begs the questions "of what?". Changeset Extraction
>> is a better name.
>
> Changeset Extraction sounds too geeky to me. Let me try some
> simplification of it. Why "set"? We capture each change; whether
> together they form a set doesn't matter much. Also, since the changes
> we're talking about occur in the stored data, I propose we use "Data
> Change" rather than "Changeset". Also, why "Extract"? We're not
> extracting these changes after the fact -- rather we capture them as
> they transit through the WAL system.
>
> So, I would propose "Data Change Capture".
How about "Change Streaming" ?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilberto Castillo | 2014-04-23 20:33:56 | Re: Let's start talking features and "theme" for 9.4 |
| Previous Message | Alvaro Herrera | 2014-04-23 19:55:48 | Re: Let's start talking features and "theme" for 9.4 |