Re: slotname vs slot_name
От | Petr Jelinek |
---|---|
Тема | Re: slotname vs slot_name |
Дата | |
Msg-id | 53902807.3080702@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: slotname vs slot_name (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Список | pgsql-hackers |
On 05/06/14 10:11, Heikki Linnakangas wrote: > 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. >>> +1 >>> 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 ? > pg_lcse or pg_lcset ? -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: