| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: slotname vs slot_name |
| Date: | 2014-06-05 08:11:02 |
| Message-ID: | 53902616.5030004@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)fujii(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2014-06-05 08:19:19 | Re: slotname vs slot_name |
| Previous Message | furuyao | 2014-06-05 08:09:44 | pg_receivexlog add synchronous mode |