| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, torikoshia(at)oss(dot)nttdata(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, gkokolatos(at)protonmail(dot)com, kasahara(dot)tatsuhito(at)gmail(dot)com, craig(at)2ndquadrant(dot)com |
| Subject: | Re: Get memory contexts of an arbitrary backend process |
| Date: | 2021-04-01 10:13:05 |
| Message-ID: | 65fbf059-bcff-1585-59a1-1ec6a6f5ac75@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021/03/31 15:16, Kyotaro Horiguchi wrote:
>> + The memory contexts will be logged based on the log configuration
>> set. For example:
>>
>> How do you think?
>
> How about "The memory contexts will be logged in the server log" ?
> I think "server log" doesn't suggest any concrete target.
Or just using "logged" is enough?
Also I'd like to document that one message for each memory context is logged.
So what about the following?
One message for each memory context will be logged. For example,
> +1 from me. It looks like more compliant with the standard?
+1, too.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2021-04-01 10:13:36 | Re: Replication slot stats misgivings |
| Previous Message | Fujii Masao | 2021-04-01 09:53:33 | Re: TRUNCATE on foreign table |