Re: Non-reserved replication slots and slot advancing

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: michael(at)paquier(dot)xyz
Cc: alvherre(at)2ndquadrant(dot)com, andres(at)anarazel(dot)de, pgsql-hackers(at)postgresql(dot)org, petr(at)2ndquadrant(dot)com, simon(at)2ndQuadrant(dot)com
Subject: Re: Non-reserved replication slots and slot advancing
Date: 2018-07-09 09:14:13
Message-ID: 20180709.181413.267703622.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello.

At Mon, 9 Jul 2018 15:48:33 +0900, Michael Paquier <michael(at)paquier(dot)xyz> wrote in <20180709064833(dot)GB30202(at)paquier(dot)xyz>
> On Mon, Jul 09, 2018 at 03:13:04PM +0900, Kyotaro HORIGUCHI wrote:
> > Looking the attached patch, I noticed that both "WAL" and "wal"
> > are used in similar ERROR messages. Grepping the source tree
> > showed me that it is always in upper case letters except in the
> > case it is a part of other words like variable/column/function
> > names or "walsender". This is the same with the word "lsn".
>
> Thanks for the lookup.
>
> I see. Indeed, let's fix at the same time the error message close by.
> xlog.c uses "WAL location (LSN)" for the same thing, so I am sticking
> with that as per the attached. I'll go commit that if there are no
> objections. If you see any others which you would like to fix, please
> feel free to send a patch.

I like it than "WAL LSN"' so I'm fine with the new message. I
don't find anything to fix in xlog.c for now.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Arthur Zakirov 2018-07-09 09:30:22 Re: Let's remove DSM_IMPL_NONE.
Previous Message David Rowley 2018-07-09 09:08:07 Re: Subplan result caching