Re: Fix pg_log_backend_memory_contexts() 's delay - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Fix pg_log_backend_memory_contexts() 's delay
Date
Msg-id YVziXut4efh+jdxR@paquier.xyz
Whole thread Raw
In response to Re: Fix pg_log_backend_memory_contexts() 's delay  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Fix pg_log_backend_memory_contexts() 's delay  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Re: Fix pg_log_backend_memory_contexts() 's delay  (bt21tanigaway <bt21tanigaway@oss.nttdata.com>)
List pgsql-hackers
On Tue, Oct 05, 2021 at 12:16:06PM -0400, Robert Haas wrote:
> Perhaps that's so, but it doesn't seem like a good reason not to make
> them more responsive.

Yeah, that's still some information that the user asked for.  Looking
at the things that have a PGPROC entry, should we worry about the main
loop of the logical replication launcher?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: pg_walinspect - a new extension to get raw WAL data and WAL stats
Next
From: Michael Paquier
Date:
Subject: Re: can we add subscription TAP test option "vcregress subscriptioncheck" for MSVC builds?