| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | amit(dot)kapila16(at)gmail(dot)com |
| Cc: | houzj(dot)fnst(at)fujitsu(dot)com, sawada(dot)mshk(at)gmail(dot)com, wangw(dot)fnst(at)fujitsu(dot)com, smithpb2250(at)gmail(dot)com, shiy(dot)fnst(at)fujitsu(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, dilipbalaut(at)gmail(dot)com |
| Subject: | Re: Perform streaming logical transactions by background workers and parallel apply |
| Date: | 2023-01-16 03:03:07 |
| Message-ID: | 20230116.120307.1055288243096760255.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Tue, 10 Jan 2023 12:01:43 +0530, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote in
> On Tue, Jan 10, 2023 at 11:16 AM Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> > Although I don't see a technical difference between the two, all the
> > other occurances including the just above (except test_shm_mq) use
> > "could not". A faint memory in my non-durable memory tells me that we
> > have a policy that we use "can/could not" than "unable".
> >
>
> Right, it is mentioned in docs [1] (see section "Tricky Words to Avoid").
Thanks for confirmation.
> Can you please start a new thread and post these changes as we are
> proposing to change existing message as well?
All right.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2023-01-16 03:12:52 | Re: Support logical replication of DDLs |
| Previous Message | Michael Paquier | 2023-01-16 02:54:46 | Re: Add LZ4 compression in pg_dump |