Re: Fix pg_log_backend_memory_contexts() 's delay

From: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
To: bt21tanigaway(at)oss(dot)nttdata(dot)com
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Subject: Re: Fix pg_log_backend_memory_contexts() 's delay
Date: 2021-10-11 05:28:19
Message-ID: be62e009ba382a1744c5700df5428ac0@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for the patch!

It might be self-evident, but since there are comments on other process
handlings in HandleAutoVacLauncherInterrupts like below, how about
adding a comment for the consistency?

/* Process barrier events */
if (ProcSignalBarrierPending)
ProcessProcSignalBarrier();

/* Process sinval catchup interrupts that happened while sleeping
*/
ProcessCatchupInterrupt();

Regards,

--
Atsushi Torikoshi
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rajkumar Raghuwanshi 2021-10-11 05:35:50 Re: Multi-Column List Partitioning
Previous Message Pavel Stehule 2021-10-11 04:31:03 is possible an remote access to some macos?