| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, nathandbossart(at)gmail(dot)com |
| Cc: | 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 12:20:09 |
| Message-ID: | 44dbf5e4-8eec-da56-daba-755128b3723e@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/7/22 21:56, Kyotaro Horiguchi wrote:
> 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.
+1.
> And since "must" is emphasized, doesn't "may" also needs emphasis?
I think emphasis only on must is fine.
Nathan, I don't see the language about being sure to persist to storage
here?
Regards,
-David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-07-08 12:22:50 | Re: Add function to return backup_label and tablespace_map |
| Previous Message | David Steele | 2022-07-08 12:01:06 | Re: Add function to return backup_label and tablespace_map |