Re: Fix pg_log_backend_memory_contexts() 's delay

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 16:16:06
Message-ID: CA+TgmobT79Q+GL+0_350Cr8qHcraiN+siUJeR3oBoMbtfL4JZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 5, 2021 at 8:28 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It's not real clear to me why we need to care about this in those
> processes' idle loops. Their memory consumption is unlikely to be
> very interesting in that state, nor could it change before they
> wake up.

Perhaps that's so, but it doesn't seem like a good reason not to make
them more responsive.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-10-05 16:23:33 Re: Role Self-Administration
Previous Message Guillaume FOREAU 2021-10-05 15:41:39 Add -java RPM generation to GDAL in pgrpms - p1