| From: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, 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-05 02:55:47 |
| Message-ID: | e1fdbdcae9fac88cf4cd4b552bc4a741@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-04-01 19:13, Fujii Masao wrote:
> 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,
Agreed.
BTW, there was a conflict since c30f54ad732(Detect POLLHUP/POLLRDHUP
while
running queries), attached v9.
Regards,
| Attachment | Content-Type | Size |
|---|---|---|
| v9-0001-add-memorycontext-elog-print.patch | text/x-diff | 26.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2021-04-05 03:20:36 | Re: Get memory contexts of an arbitrary backend process |
| Previous Message | Michael Paquier | 2021-04-05 02:20:08 | Re: [PATCH] typo fix in collationcmds.c: "if they are distinct" |