Re: slotname vs slot_name - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: slotname vs slot_name
Date
Msg-id 53902616.5030004@vmware.com
Whole thread Raw
In response to Re: slotname vs slot_name  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: slotname vs slot_name  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-hackers
On 06/05/2014 05:09 AM, Amit Langote wrote:
> Hi,
>
> On Thu, Jun 5, 2014 at 10:57 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> I like using "slot_name" everywhere, i.e, even in recovery.conf.
>> primary_slot_name seems not so long name.
>>
>> BTW, what about also renaming pg_llog directory? I'm afraid that
>> a user can confuse pg_log with pg_llog.
>>
>
> Recently I came across this while tab-completing pg_log ;-)
> I remember asking to document pg_llog elsewhere.

+1 for renaming pg_llog. We have all heard the stories of people 
deleting pg_clog because "it's just logs". I feel that pg_llog might be 
an even greater risk at that (although the consequences are not as 
serious as deleting pg_clog.

pg_ldecoding ?


- Heikki



pgsql-hackers by date:

Previous
From:
Date:
Subject: pg_receivexlog add synchronous mode
Next
From: Petr Jelinek
Date:
Subject: Re: slotname vs slot_name