Re: slotname vs slot_name

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: 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 17:56:10
Message-ID: 62741a67-eddd-4ed3-82a4-c181a1ac9f66@email.android.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Andres

--
Please excuse brevity and formatting - I am writing this on my mobile phone.

Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2014-06-05 18:14:55 Re: recovery testing for beta
Previous Message Tom Lane 2014-06-05 17:43:06 Re: slotname vs slot_name