Re: Fix pg_log_backend_memory_contexts() 's delay

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, bt21tanigaway <bt21tanigaway(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix pg_log_backend_memory_contexts() 's delay
Date: 2021-10-05 23:40:14
Message-ID: YVziXut4efh+jdxR@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-10-05 23:43:12 Re: can we add subscription TAP test option "vcregress subscriptioncheck" for MSVC builds?
Previous Message Jeremy Schneider 2021-10-05 22:30:07 Re: pg_walinspect - a new extension to get raw WAL data and WAL stats