| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Printing backtrace of postgres processes |
| Date: | 2022-01-24 16:36:07 |
| Message-ID: | 850fa46c-73b8-47cb-901a-090ef036a741@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022/01/24 16:35, torikoshia wrote:
> On 2022-01-14 19:48, Bharath Rupireddy wrote:
>> On Sat, Nov 20, 2021 at 11:50 AM Bharath Rupireddy
>> <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>>>
>>> On Fri, Nov 19, 2021 at 4:07 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
>>> > The Attached v15 patch has the fixes for the same.
>>>
>>> Thanks. The v15 patch LGTM and the cf bot is happy hence marking it as RfC.
>>
>> The patch was not applying because of the recent commit [1]. I took
>> this opportunity and tried a bunch of things without modifying the
>> core logic of the pg_log_backtrace feature that Vignesh has worked on.
I have one question about this feature. When the PID of auxiliary process like archiver is specified, probably the function always reports the same result, doesn't it? Because, for example, the archiver always logs its backtrace in HandlePgArchInterrupts().
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | samay sharma | 2022-01-24 16:41:39 | Re: Error running configure on Mac |
| Previous Message | Peter Eisentraut | 2022-01-24 16:32:08 | Re: makefiles writing to $@ should first write to $@.new |