| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: slotname vs slot_name |
| Date: | 2014-06-05 11:13:58 |
| Message-ID: | 539050F6.6050300@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/05/2014 02:10 PM, Magnus Hagander wrote:
> On Thu, Jun 5, 2014 at 12:57 PM, Andres Freund <andres(at)2ndquadrant(dot)com>
> wrote:
>
>> We have:
>> * pg_ldecoding (Heikki)
>> * pg_lcse or pg_lcset (Petr)
>> * pg_logical (Andres)
>>
>> I like, what a surprise, my own suggestion best. The name seems more
>> versatile because it's not restricted to decoding.
>>
> I don't care too much really, either one is find - but if I should vote,
> I'll split my vote between pg_locical and pg_ldecoding, I don't like lcse
> and lcset very much.
pg_changesets ?
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-06-05 11:18:19 | Re: slotname vs slot_name |
| Previous Message | Heikki Linnakangas | 2014-06-05 11:12:31 | Re: slotname vs slot_name |