Horton

Re: Fix pg_log_backend_memory_contexts() 's delay

torikoshia <torikoshia@oss.nttdata.com>

View thread View on postgr.es
From: torikoshia <torikoshia@oss.nttdata.com>
To: bt21tanigaway@oss.nttdata.com
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Date: 2021-10-11T05:28:19Z
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

Commits

  1. Make autovacuum launcher more responsive to pg_log_backend_memory_contexts().