| From: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, 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 19:53:17 |
| Message-ID: | 5390CAAD.5030809@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/06/14 19:56, Andres Freund wrote:
> On June 5, 2014 7:43:06 PM CEST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>>> Robert Haas wrote:
>>>> For my part, I'd strongly prefer a name based on the term "logical
>>>> decoding".
>>
>>> There is no reason not to use long names, so I think
>> pg_logical_decoding
>>> is fine.
>>
>> +1
>
> Still not a fan oft having decoding in the name. I've at least one patch pending (replication identifiers, submitted a couple months back) that will need to stash a couple of files somewhere. And it's for the apply side, not the decoding side.
>
Personally I like your suggestion of pg_logical
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Linos | 2014-06-05 21:09:46 | Re: performance regression in 9.2/9.3 |
| Previous Message | Jeff Janes | 2014-06-05 18:14:55 | Re: recovery testing for beta |