Re: remove more archiving overhead

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: nathandbossart(at)gmail(dot)com
Cc: david(at)pgmasters(dot)net, robertmhaas(at)gmail(dot)com, masao(dot)fujii(at)oss(dot)nttdata(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: remove more archiving overhead
Date: 2022-07-08 01:56:52
Message-ID: 20220708.105652.1551158050191356887.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 7 Jul 2022 15:07:16 -0700, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote in
> Here's an updated patch.

Thinking RFC'ish, the meaning of "may" and "must" is significant in
this description. On the other hand it uses both "may" and "can" but
I thinkthat their difference is not significant or "can" there is
somewhat confusing. I think the "can" should be "may" here.

And since "must" is emphasized, doesn't "may" also needs emphasis?

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo NAGATA 2022-07-08 02:07:44 Re: Add a test for "cannot truncate foreign table"
Previous Message Masahiko Sawada 2022-07-08 01:14:25 Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns